Document 29

SEBoK *System Validation*, Distilled

framework

SEBoK System Validation, Distilled

Top-20 distillation #11. System Validation is the SEBoK page that completes the V&V pair with SE-025 System Verification and provides empirical confirmation of Doc 445's Refinement A (paired pulverization with two anchors). The "glass box vs black box" perspective distinction names Doc 445's $T_I$ (internal coherence) vs $T_E$ (external correspondence) anchors directly. Three validation types (Continuous / Final / Operational) compose under Doc 572 lattice and Doc 270 pin-art over time. "Level Per Level" hierarchical application is per-rung pulverization. Pitfalls listed (deferring validation, exclusive reliance on testing) map to Doc 574 authority-evacuation patterns. Six corpus forms compose; no new residuals; this is the canonical empirical witness for the Refinement A pair pattern.

I. Source

II. Source Read

System Validation is "the set of activities that ensure and provide confidence that a system is able to accomplish its intended use, goals, and objectives." Distinct from verification: verification is "Done Right" (state-of-the-art compliance, glass-box, supplier-oriented); validation is "Does Right" (expected effect, black-box, end-user-oriented). Verification's baseline is system design; validation's baseline is stakeholder requirements. Verification first; validation second. Process: establish strategy → perform actions → analyze results → control. Methods identical to verification techniques but with different intent. Three types: Continuous (throughout development), Final (integrated system in industrial environment), Operational (actual environment with real operators). "Level Per Level" hierarchical application before integration. Standards: ISO 9000:2005, 15288:2015, NASA SEH 2007, INCOSE SEH v3.2.2.

III. Structural Read

Form VI — Pulverization (Doc 445), with Refinement A confirmed. The page is the canonical empirical witness for Doc 445 Refinement A's paired pulverization pattern. SEBoK's "glass box vs black box" frame names the two anchor points directly:

  • Glass box (verification) = $T_I$ in Doc 445's notation = internal coherence reference (the system's own design references).
  • Black box (validation) = $T_E$ in Doc 445's notation = external correspondence reference (stakeholder intent and operational success).

The full notation under Refinement A reads system V&V as $T = \langle T_I, T_E \rangle$ exactly. Verification residuals are defects (glass-box failures); validation residuals are misalignments (black-box failures). The distinction is structurally load-bearing in SE practice and the corpus's apparatus reads it precisely.

Form VI extension — Refinement B confirmed. "Methods are identical to verification techniques but applied with different intent" is direct evidence that the six rigor levels (Inspection / Analysis / Analogy / Demonstration / Test / Sampling) are anchor-independent. The same level applies under either anchor; what differs is what is being pulverized. This is independent confirmation that Refinement B's calibration is general across both V&V activities.

Form III (extension) — Lattice Extension of the Ladder (Doc 572). "Level Per Level" hierarchical application — validation at each decomposition level before integration — is per-rung pulverization across a Pattern-layer chain. The decomposition rungs sibling-bind under universal-rung pulverization (Doc 572 Appendix D's universal-sibling pattern with pulverization as the binding). Three validation types (Continuous / Final / Operational) are temporal-concurrency lattice (Doc 572 Appendix C): they sibling-bind the engagement at different temporal aspects.

Form IV — Pin-Art Model (Doc 270). Validation actions, validation procedures, validation tools, validation configurations together compose pin-art at the V activity rung. The discipline of structuring V activities is itself pin-art applied to V; this is recursive pin-art the corpus already permits in Doc 270's apparatus.

Form XII — Authority Evacuation (Doc 574 / Doc 571 evacuated state). The page's listed pitfalls — "deferring validation until project completion," "relying exclusively on testing," "discontinuing validation when budget diminishes" — are authority-evacuation patterns at the V activity. The validation function is occupied formally (the activity is on the project plan) but evacuated structurally (no resources, no authority, no continued binding). Doc 574 reads each pitfall as an evacuation pattern with a specific evacuation mechanism: temporal deferral (push the activity past the budget horizon), narrowing (constrain the activity to one technique), starvation (withdraw resources mid-project).

Form III — Substrate-and-Keeper Composition (Doc 510). "Involve end-users directly in acceptance testing" is the multi-keeper case again (SE-023 surfaced this candidate): validation requires end-users to participate as co-keepers of the validation process. The SE keeper supplies the validation framework; the end-user keeps the criterion of "Does Right." Without end-user participation, validation collapses into verification.

IV. Tier-Tags

  • Validation definition — π / α (well-cited; ISO 9000, INCOSE).
  • The verification-vs-validation distinction (Done Right vs Does Right; glass box vs black box; supplier vs user) — π / α as cited; μ / β under corpus when read as Doc 445 Refinement A canonical empirical instance.
  • Three validation types (Continuous / Final / Operational) — π / α; μ / β under corpus when read as Doc 572 Appendix C temporal-concurrency lattice.
  • "Level Per Level" hierarchical application — π / α; μ / β under corpus when read as universal-rung pulverization.
  • Pitfalls (deferring / exclusive testing / starvation) — π / α as cited; μ / β under corpus when read as Doc 574 evacuation patterns.
  • "Methods are identical to verification techniques but applied with different intent" — π / α; μ / β under corpus as Refinement B independence confirmation.

V. Residuals

No residuals against the apparatus. The page composes cleanly under existing forms with both Doc 445 refinements confirmed empirically. This is one of the most clean-composing SEBoK pages observed in the top-20 set.

VI. Provisional Refinements

No new refinement candidates. The page provides empirical CONFIRMATION of refinements landed in Doc 445 (Refinements A and B) and Doc 572 (Appendix C temporal concurrency, Appendix D universal-sibling). The form's apparatus reads validation as expected.

The "involve end-users directly" claim adds modest weight to the multi-keeper composition extension candidate (Doc 510 / SE-023) but does not yet supply a second independent case; the multi-keeper extension remains deferred.

VII. Cross-Links

Form documents. Doc 445 (Pulverization, with Refinements A and B), Doc 572 (Lattice Extension, with Appendices C and D), Doc 270 (Pin-Art), Doc 510 (Substrate-and-Keeper), Doc 574 (Authority Evacuation, now Doc 571 evacuated state).

Part-level reformulation. SE-006 (Part 3 — SE & Management).

Related distillations. SE-025 (System Verification — V&V counterpart). SE-022 (Generic Life Cycle Model — V&V is transverse). Doc 580 (Hubble — V&V failure case).

Adjacent SEBoK concepts (per source). System Verification, System Integration, System Transition, System Operation, Quality Management.

Appendix: Originating Prompt

"Continue with next 10" (in context of Top-20 SEBoK distillations after Doc 583 methodology and refinements landed).

(SE-029 is the eleventh of twenty. System Validation was selected as the V&V counterpart to SE-025; it provides empirical confirmation of Doc 445's Refinements A and B and of Doc 572's temporal-concurrency and universal-sibling appendices. No new residuals; the apparatus reads the page as expected. This is the form working.)

Referenced Documents

More in framework