Document 70

SEBoK *Domain Specific Systems Engineering Guidances / Application of Systems Engineering Standards*, Distilled

framework

SEBoK Domain Specific Systems Engineering Guidances / Application of Systems Engineering Standards, Distilled

Next-40 distillation, batch 4 doc 7. SEBoK's Application of Systems Engineering Standards (Part 3, SE Standards) is the canonical surface for domain-specific guidance: rather than enumerate per-domain standards, the page formalizes the universal tailoring discipline that every domain applies to general SE standards. The shall/should/can language taxonomy, the conformance-vs-compliance distinction, and the three-level conformance regime (full / tailored / agreement-based) per ISO/IEC/IEEE 15288:2023 are universal-sibling lattice (Doc 572 Appendix D) at the standards-application rung. Tailoring itself is a co-production discipline (Doc 573) between the standard-keeper and the domain-keeper. Five corpus forms compose; tailoring as canonical co-production worked example.

I. Source

II. Source Read

Standards are "agreed upon, repeatable way[s] of doing something" designed for voluntary adoption that "can become mandatory through legislation, contracts, or organizational policy." Language taxonomy: "shall" (strict requirements, no deviation), "should" (recommended, flexibility allowed), "can" (permissible, preferred over "may"). Conformance vs. compliance: conformance is "voluntary alignment with consensus standards, often self-imposed for operational uniformity"; compliance is "adherence to mandatory legal/regulatory requirements, typically enforced by external authorities." Conformance claims must identify which requirements are satisfied per the standard's Conformance Clause. ISO/IEC/IEEE 15288:2023 recognizes three conformance levels: full conformance (all requirements satisfied), tailored conformance (selected requirements modified appropriately), agreement-based compliance (standards incorporated into contracts between acquirers and suppliers). "Life cycle models, as well as the processes from ISO/IEC/IEEE 15288, may be adapted for an individual project to reflect the variations appropriate to the organization, project and system while still being able to claim tailored conformance." Position: Part 3, SE Standards.

III. Structural Read

Form A (universal-sibling lattice, Doc 572 Appendix D). Three Cluster A candidates appear on this single page. (i) The shall / should / can language taxonomy is universal-sibling at the requirement-language rung: every requirement in every standard carries one of three modal commitments, the discriminator is modal-aspect. (ii) Conformance / compliance is universal-sibling at the obligation-source rung: every standard adoption sits in one of two obligation-regimes simultaneously possible. (iii) The three conformance levels (full / tailored / agreement-based) are universal-sibling at the conformance-mode rung: every conformance claim sits in exactly one mode. Cluster A membership extends to nine.

Form D (co-production at sub-rungs, Doc 573). Tailoring is canonical co-production. The standard-keeper (the SDO) supplies the requirement set and Conformance Clause (rung-2 affordance); the domain-keeper (the adopting organization) supplies the project context and the tailoring decisions (rung-1 substrate). Neither alone produces the tailored conformance; the two compose at the conformance rung. The three-level taxonomy makes this explicit: full conformance is keeper-dominated, tailored is balanced, agreement-based is contract-mediated. This is one of the cleanest co-production worked examples in the SEBoK surface.

Form E (institutional ground, Doc 571). ISO/IEC/IEEE 15288:2023, ISO 9001, ISO 14000, and 24748-2:2024 are institutional ground. The Conformance Clause itself is an institutional-ground primitive: a standard that lacks a Conformance Clause cannot ground tailored conformance because there is no formal-authority component to the substrate-side claim. Cluster E membership extends.

Form C (architectural school, Doc 538). Domain-specific tailoring is school-pluralism. Aerospace tailors 15288 differently than automotive, medical, or financial-services contexts. The tailoring-as-school is a meta-school: each domain's accumulated tailoring tradition is itself a school under Doc 538. The article gestures at this without enumerating; the corpus reads the absence of per-domain enumeration as deliberate generality (the universal tailoring discipline is what travels; the per-domain content is keeper-authored by each domain).

Form K (virtue constraints, Doc 314). The conformance-vs-compliance distinction brushes V3 (truth-telling) at the engineering-decision layer. A "tailored conformance" claim that omits the actual tailoring decisions is structurally a V3 violation; the Conformance Clause discipline (identify what specific requirements are satisfied) is the apparatus enforcing V3 at the standards-application rung.

IV. Tier-Tags

  • Standards as voluntary frameworks — π / α as cited.
  • Shall / should / can taxonomy — π / α as cited; μ / β under Doc 572 Appendix D at requirement-language rung.
  • Conformance vs. compliance distinction — π / α as cited; μ / β under Doc 572 Appendix D at obligation-source rung.
  • Three conformance levels — π / α as cited; μ / β under Doc 572 Appendix D at conformance-mode rung.
  • Tailoring discipline — π / α as cited; μ / β under Doc 573 co-production.
  • Conformance Clause requirement — π / α; corpus reads as V3 enforcement primitive.

V. Residuals

No structural residuals. The page is unusually structurally dense: three Cluster A candidates plus a canonical Doc 573 worked example on a single article. The absence of per-domain enumeration is structurally correct: domain-specific guidance is the corpus's name for what each domain-keeper supplies; SEBoK's job at this page is the universal tailoring grammar, not the per-domain content.

VI. Provisional Refinements

Doc 573 canonical-example update candidate. Tailoring is a cleaner co-production worked example than the requirements-as-co-production case originally used in Doc 573. Tailoring has explicit institutional ground (Conformance Clause), explicit three-level taxonomy, and explicit roles for both keepers. Consider promoting tailoring to Doc 573's primary canonical example, with requirements-as-co-production as the secondary case.

VII. Cross-Links

Form documents. Doc 572 Appendix D (universal-sibling lattice, three candidates on one page), Doc 573 (Co-production, tailoring as canonical worked example), Doc 571 (Institutional Ground, Conformance Clause), Doc 538 (Architectural School, per-domain tailoring traditions), Doc 314 §9.5 (V3 at engineering-decision layer).

Part-level reformulation. SE-006 (Part 3 SE and Management).

Related distillations. SE-068 (Why Standards, this batch). SE-069 (Alignment and Comparison of SE Standards, this batch). SE-066 (Life Cycle Concepts, no-one-size-fits-all). SE-030 (Stakeholder Needs, co-production).

Adjacent SEBoK concepts. Why Standards?, Alignment and Comparison of Systems Engineering Standards, Systems Engineering Related Standards Landscape, Healthcare Systems Engineering, Systems Engineering and Software Engineering.

Appendix: Originating Prompt

"Let's do the next 40 most likely articles to be most load bearing... 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-070 is one of the next-40 SEBoK distillations. Batch 4/5.)

Referenced Documents

More in framework