Document 40

SEBoK *System Definition*, Distilled

framework

SEBoK System Definition, Distilled

Next-40 distillation #1 (Batch 1/5). System Definition is the SEBoK umbrella term for the front-end technical activities of an engagement: concept definition, requirements definition, architecture design definition, and detailed design definition. The four sub-knowledge-areas form a universal-sibling lattice (Doc 572 Appendix D) at the front-end-engineering rung; the discriminator is aspect (concept-aspect, requirements-aspect, architecture-aspect, detail-aspect) rather than rung-of-application. The umbrella's pin-art temporal staging (Doc 270 / Doc 572 Appendix C) reads as concurrent and recursive across the four sub-KAs, not strictly sequential. Affordance-gap (Doc 530) is dense here: System Definition is precisely the rung-2 supply phase where keeper-side intent meets substrate's rung-1 producibility. Five corpus forms compose; cluster-density shift noted under provisional refinements.

I. Source

II. Source Read

System Definition is the SEBoK umbrella term for the core front-end technical activities of systems engineering, defined in the glossary as "a set of core technical activities of systems engineering, including the activities that are completed primarily in the front-end portion of the system design." The umbrella covers four constituent knowledge areas as currently organized within Part 3 (Systems Engineering and Management): (1) System Concept Definition (business/mission analysis, stakeholder needs); (2) System Requirements Definition (translating needs into specified requirements); (3) System Architecture Design Definition (functional, logical, and physical architectures); (4) System Detailed Design Definition (element-level design refinement). The activities align with the concept stage in the ISO/IEC/IEEE 15288 life cycle and the INCOSE Handbook v5.0 articulation. System Definition outputs feed System Realization (implementation, integration, verification, validation) and ultimately System Deployment and Use. Standards cited across the constituent KAs: ISO/IEC/IEEE 15288:2023, INCOSE SE Handbook v5.0, IEEE 1220, NASA Systems Engineering Handbook, ECSS-E-ST-10C.

III. Structural Read

Form III (extension) — Lattice Extension of the Ladder (Doc 572), with Appendix D universal-sibling at the front-end-engineering rung. The four sub-KAs (concept, requirements, architecture, detail) are universal-sibling lattice. Each binds every system under definition; the discriminator is aspect, not rung-of-application. This is the seventh Appendix D instance (after requirement types SE-024, architecture views SE-031, competency dimensions SE-033, CMMI measures SE-034, MODA value axes SE-036, HSI domains SE-038). The partition's specifics are keeper-authored content; the structure is universal-sibling lattice.

Form IV — Pin-Art Model (Doc 270), composed with Doc 572 Appendix C temporal-concurrency. The four sub-KAs are not executed serially. Concept iterates as architecture surfaces feasibility constraints; requirements refine as detail design exposes implementability; the substrate's accumulated working knowledge flows through all four concurrently. The umbrella's temporal posture is the same concurrency-iteration-recursion the Process Concepts page (SE-044) names explicitly.

Form II — Affordance Gap (Doc 530), at peak density. System Definition is the rung-2 supply phase. The keeper-side declares intent (concept), specifies requirements, sketches architecture, and elaborates detail; the substrate (engineering practice, technology, the engineered artifact) holds the affordances. The four sub-KAs are four passes across the affordance gap, each at finer resolution. Doc 530's apparatus binds densely here; System Definition is one of the canonical Cluster J locations.

Form XI — Co-Production at Sub-Rungs (Doc 573). Each of the four sub-KAs is itself a co-production engagement (concept co-produced with stakeholders per SE-023, requirements co-produced per SE-030, architecture co-produced with domain experts, detail design co-produced with implementation specialists). The umbrella inherits the co-production structure across all four. Multi-keeper composition (Doc 510 / Doc 604) binds at the umbrella rung where the four sub-KA outputs reconcile.

Form V — Hypostatic Boundary (Doc 372). System Definition specifies what the system will DO, what constraints it must satisfy, what shape it will take. The discipline does not specify what the system IS in any ontological sense. Doc 372's reading discipline holds; the architecture-as-formalization is structural, not ontological.

IV. Tier-Tags

  • System Definition glossary definition (front-end core technical activities) — π / α as cited.
  • Four-KA decomposition (concept / requirements / architecture / detail) — π / α as cited; μ / β under corpus when read as Doc 572 Appendix D universal-sibling lattice at the front-end rung.
  • Concurrent-iterative-recursive execution claim — π / α as cited (cross-references Process Concepts); μ / β under corpus as Doc 270 / Doc 572 Appendix C temporal-concurrency.
  • Alignment with ISO 15288 concept stage — π / α as cited.

V. Residuals

No structural residuals against the apparatus. The umbrella reads cleanly as universal-sibling lattice composed with temporal-concurrency. The seventh Cluster A instance further densifies an already-dense cluster.

VI. Provisional Refinements

Cluster A density now seven instances; cluster-strength threshold for cluster-level synthesis approached. SE-039 Cluster A had six members at the time of writing; SE-040 brings it to seven. Per SE-039 §V step 3 (cluster-level deep passes when membership exceeds ~10 instances), Cluster A is approaching the threshold. The remaining Batch 1–5 articles will likely add several more (Process Concepts, Life Cycle Models, Development Approaches each plausibly contribute Cluster A members). A Cluster A synthesis successor to Doc 604 may be warranted by end of next-40 sweep.

Cluster J (affordance gap) candidate densification. System Definition is dense Cluster J territory but the cluster has only three named members in SE-039. Adding System Definition (SE-040) brings Cluster J to four; Batch 2–5 plausibly adds more.

VII. Cross-Links

Form documents. Doc 572 (Lattice Extension, Appendix D — seventh instance), Doc 270 (Pin-Art), Doc 530 (Affordance Gap), Doc 573 (Co-Production at Sub-Rungs), Doc 510 / Doc 604 (Multi-keeper composition), Doc 372 (Hypostatic Boundary).

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

Related distillations. SE-023 (System Concept Definition — sub-KA #1). SE-024 (Types of System Requirements — feeds sub-KA #2). SE-030 (Stakeholder Needs Definition — feeds sub-KA #1/#2). SE-031 (System Architecture — sub-KA #3). SE-041 (System Realization — successor umbrella).

Adjacent SEBoK concepts (per source). System Concept Definition, System Requirements Definition, System Architecture Design Definition, System Detailed Design Definition, System Realization.

Methodology refinement candidates. Cluster A approaching cluster-level synthesis threshold (seven of ten instances).

Appendix: Originating Prompt

"Let's do the next 40 most likely articles to be most load bearing (at the top of the hierarchy) my conjecture is that this will inform the next 40."

"It's ok to duplicate entries. It shows where the knowledge base folds back in on itself. Continue fanning out"

(SE-040 is one of the next-40 SEBoK distillations. Batch 1/5.)

Referenced Documents

More in framework