SEBoK Requirements Flow Down and Allocation, Distilled

Fifth-batch SEBoK distillation, batch 3/5, doc 4 of 8. SEBoK has no standalone Requirements Allocation or Requirements Flow Down page (404 on prompt-named URL and Allocation_of_System_Requirements alternate; Stakeholder_Requirements_Definition exists only as a redirect with no content). The discipline lives dispersed across System Requirements, System Requirements Definition, System Architecture, System Architecture Design Definition, and Stakeholder Needs and Requirements Definition — D8 internal-migration mode (SE-039 §VII.6/§VII.7), no anchor article. SE-179 is structurally a dispersed-instrument distillation read against the matured taxonomy: the formalization rung migrated into SEBoK and is carried by the surrounding architecture-and-requirements-definition pages. The reading is consistent with §VII.6's eight 404'd target observation (Stakeholder Requirements Definition listed as 404) and confirms that requirements-flow-down-and-allocation is structurally one of the deepest D8 instances — the discipline is so universally distributed across SE's process surface that no single page hosts it. The corpus's SE-044 (Process Concepts) anchor for Cluster I (pin-art / temporal-concurrency) is implicated: requirements flow-down is itself a temporal-concurrency operation across architecture rungs (system → subsystem → component), with traceability binding the flow longitudinally (Cluster F Refinement D, Doc 445). The dispersion is informative: the formalization is so foundational that it migrated into surrounding pages rather than concentrating. Five clusters compose; D8 internal-migration confirmed at SE-process-foundation rung.

---

I. Source

• Page: Requirements Flow Down and Allocation — does not exist on SEBoK (404 on prompt-named URL; Allocation_of_System_Requirements 404; Stakeholder_Requirements_Definition is a redirect-only with no content)
• URL attempted: https://sebokwiki.org/wiki/Requirements_Allocation, /Allocation_of_System_Requirements
• Carrier surface (internally dispersed): System Requirements, System Requirements Definition, System Architecture, System Architecture Design Definition, Stakeholder Needs and Requirements Definition
• License: CC BY-SA 3.0 (SEBoK)
• Retrieved: 2026-04-29

II. Source Read

The discipline of requirements flow-down and allocation is the SE-process-foundation operation that decomposes higher-rung requirements into lower-rung requirements while preserving traceability across rungs. SEBoK's articulation lives across multiple pages: stakeholder needs (top rung) decompose to system requirements (rung-1 below), system requirements decompose to subsystem requirements (rung-2 below), subsystem requirements decompose to component requirements (rung-3 below). At each rung-transition, the keeper-side allocation discipline binds: which sub-substrate carries which requirement-share, with what traceability link, with what verification handoff. The discipline's institutional carrier-set includes ISO/IEC/IEEE 29148 (requirements engineering), ISO/IEC/IEEE 15288 (lifecycle processes), INCOSE NRM 2022 (requirements writing rules). The retrieval found no SEBoK page that hosts the discipline at concentration; the discipline is carried by the surrounding architecture-and-requirements-definition pages, with each page contributing a rung-aspect of the larger flow-down-and-allocation operation.

III. Structural Read

Cluster J D8 (internal-migration mode, SE-039 §VII.6/§VII.7) at SE-process-foundation rung. Requirements flow-down and allocation is structurally one of the deepest D8 instances yet observed: the discipline is so universally distributed across SE's process surface that every Part 3 process page implicitly assumes flow-down-and-allocation, every architecture page operates at one rung of the flow-down lattice, and no single page hosts the discipline at concentration. The dispersion is informative: the formalization is foundational rather than peripheral — what migrates internally is the load-bearing core of SE's process discipline, not its margins. SE-179 anchors D8 at SE-process-foundation rung; together with SE-177 (D8 at industry-application-domain rung) the D8 mode now has two distinct rung-scopes anchored.

Cluster F (pulverization, Doc 445) Refinement D longitudinal-pulverization at flow-down-traceability rung. The flow-down-and-allocation discipline preserves traceability across rungs and across time: each lower-rung requirement traces back to its higher-rung parent, and the trace must be preserved across the system lifecycle. This is Refinement D longitudinal-pulverization (Doc 445, anchor SE-097 CM, anchor-reassignment-candidate SE-114 IM per §VII.6). Requirements flow-down is structurally one of the cleanest Refinement D instances: the trace is the longitudinal-pulverization substrate; the discipline of writing the trace, maintaining it across changes, and verifying it at handoffs is the longitudinal-pulverization operation. The §VII.6 anchor-reassignment-to-IM proposal is reinforced: requirements traceability is the IM discipline operating at the requirements rung.

Cluster I (pin-art / temporal-concurrency, Doc 270 / Doc 572 Appendix C) flow-down across rungs as concurrent operation. SE-044 (Process Concepts) anchors Cluster I per SE-039 D7. Requirements flow-down operates concurrently across rungs in the matured-SE practice: system-rung requirements are not finalized before subsystem-rung allocation begins; instead, flow-down and elaboration at lower rungs feeds back up into refinement at higher rungs, with the concurrent operation integrated at gate-and-review pin-art instants. Cluster I extends with a flow-down-as-concurrency sub-instance.

Cluster A (universal-sibling lattice, Doc 572 Appendix D) allocation-criterion lattice. The criteria for allocating a requirement to a sub-substrate (functional-fit, performance-budget, interface-locality, technology-readiness, cost, schedule, risk, supplier-capability) are universal-sibling at the allocation-decision rung — each criterion binds every allocation decision aspect-wise; the discriminator is criterion-aspect. The lattice is implicit in SEBoK's coverage rather than enumerated; the corpus reads it as universal-sibling regardless. Cluster A density continues.

Cluster B (multi-keeper composition, Doc 604) keeper-coordination-across-rungs. Flow-down and allocation composes the system-keeper, the subsystem-keepers, the component-keepers, and the verification-keeper at each rung. The composition rule is coordination-by-rung (Doc 604 already-formalized) operating recursively: each rung-transition composes a higher-rung-keeper with one or more lower-rung-keepers under coordination-by-rung; the recursive composition produces the full flow-down lattice. Convergent with SE-037 SE-PM coordination-by-rung at engagement scope; flow-down-and-allocation extends coordination-by-rung to architectural-rung scope. Worth flagging: vertical-composition (SE-039 §VII.7 #2 candidate, SE-152 PfM-SE-PM first instance) reads cleanly here. Flow-down-and-allocation is the canonical vertical-composition operation; SE-152 ascends from project to portfolio (management rungs), SE-179 descends from system to component (architectural rungs). Two-instance vertical-composition: ascending and descending. Vertical-composition promoted from candidate (one instance) to formalization-ready (two instances at distinct rung-types).

IV. Tier-Tags

• Requirements flow-down editorial absence — π (observation) / α (verbatim 404 retrieval).
• Carrier-page distribution (System Requirements, System Architecture, etc.) — π / α as cited.
• ISO/IEC/IEEE 29148, 15288, INCOSE NRM 2022 institutional carriers — π / κ (corpus knowledge of requirements-engineering institutional surface).
• Allocation-criterion lattice — π / κ; μ / β under Cluster A density extension.
• Vertical-composition descending-architectural-rungs instance — μ / β under SE-039 §VII.7 #2 promotion.

V. Residuals

Foundational dispersion observation. What migrates internally as D8 may be the most foundational SE operations rather than the least — flow-down-and-allocation is structurally inescapable in SE practice; its dispersion is structural saturation rather than editorial neglect. Worth flagging when D8 sub-modes are next formalized.

Vertical-composition's dual-rung-type structure. SE-152 (ascending: project → program → portfolio) and SE-179 (descending: system → subsystem → component) are dual instances of vertical-composition at distinct rung-types. The structural pair sharpens vertical-composition's definition: it is keeper-composition across an ordered rung-stack, where the rung-stack may be ascending (management hierarchy) or descending (architectural hierarchy). The dual-rung-type may itself be a sub-form distinction.

VI. Provisional Refinements

Vertical-composition (SE-039 §VII.7 #2) promoted from candidate to formalization-ready. Two instances now (SE-152 ascending-management, SE-179 descending-architectural); the dual-rung-type structure (ascending vs. descending ordered stacks) sharpens the definition. Doc 604 next refinement round should formalize as Cluster B sub-form distinct from horizontal multi-keeper.

Cluster F Refinement D anchor reassignment to IM is further reinforced. §VII.6 proposed reassigning Refinement D's anchor from CM (SE-097) to IM (SE-114) since IM is structurally the more general substrate-preservation discipline; SE-179 supplies a fourth sub-rung validation (after CM/SE-097, TRA/SE-141, DE/SE-110): requirements-traceability/SE-179. Reassignment is now near-formalization.

D8 sub-mode candidate: foundational-saturation vs. peripheral-dispersion. SE-179's reading suggests D8 has two sub-modes: foundational-saturation (the discipline is so universally distributed that its dispersion is structural; e.g., requirements flow-down) and peripheral-dispersion (the discipline is editorially scattered; e.g., Lessons Learned per SE-092). Awaiting second foundational-saturation instance to confirm.

VII. Cross-Links

Form documents. SE-039 §VII.6/§VII.7 (entracement, D8 SE-process-foundation rung; foundational-saturation sub-mode candidate; #2 vertical-composition formalization-ready), Doc 445 (pulverization, Refinement D longitudinal at flow-down-traceability rung; IM anchor-reassignment fourth validation), Doc 270 / Doc 572 Appendix C (pin-art / temporal-concurrency, flow-down-as-concurrency sub-instance), Doc 572 Appendix D (universal-sibling, allocation-criterion lattice), Doc 604 (multi-keeper, vertical-composition formalization-ready).

Part-level reformulation. SE-006 (Part 3 SE and Management) — flow-down is the Part 3 process backbone; the dispersion across Part 3 pages is the structural reading.

Related distillations. SE-044 (Process Concepts, Cluster I anchor), SE-097 (CM, Refinement D anchor predecessor), SE-114 (IM, Refinement D anchor-reassignment target), SE-152 (PfM-SE-PM, vertical-composition ascending first instance), SE-092 (Lessons Learned, peripheral-dispersion D8 contrast).

Adjacent SEBoK concepts (carrier surface). System Requirements, System Requirements Definition, Stakeholder Needs and Requirements Definition, System Architecture, System Architecture Design Definition.

Methodology refinement candidates. Vertical-composition formalization with dual-rung-type sub-form; D8 foundational-saturation vs. peripheral-dispersion sub-mode distinction; Refinement D IM anchor-reassignment near-formalization.

---

Appendix: Originating Prompt

"Add an entrancing section..." / "Yes. And then continue..."

(SE-179 is the fourth of eight in batch 3/5 of the fifth-batch SEBoK distillation sweep. Editorial-absence reading at SE-process-foundation rung; D8 foundational-saturation sub-mode candidate. Vertical-composition (#2) promoted from candidate to formalization-ready via dual-rung-type pair with SE-152. Batch 3/5.)

---