Document 125

SEBoK *Requirements Management*, Distilled

framework

SEBoK Requirements Management, Distilled

Fourth-batch SEBoK distillation, batch 1 doc 6. Requirements Management (Part 3 Technical Management Processes) defines RM as "performed to ensure alignment of requirements with other representations, analyses, and system artifacts generated across the life cycle." Authors Tami Katz (lead), Lou Wheatcraft, Mike Ryan; sources INCOSE NRM 2022 and INCOSE GtNR 2022. Eight cross-cutting activities (managing definition, baselining, communicating, flow-down, interfaces, traceability, V&V artifacts, change). This batch was prompt-flagged as the Cluster A multi-rung lattice (Doc 572 D.6) stress-test article. The Doc 572 D.6 multi-rung reading binds sharply: RM operates at four nested rungs simultaneously (artifact rung, process-step rung, technical-management-process rung, life-cycle rung). Six clusters compose. Cluster A binds at four nested rungs and on three independent partitions (eight activities, six change drivers, five RMT capabilities) plus the lattice-multi-rung composition itself. Cluster F binds bidirectionally. Cluster I binds via cross-life-cycle concurrency. Cluster B binds with three-author keeper composition. Cluster D binds via stakeholder-engineer co-authored requirements. Cluster E binds via INCOSE NRM/GtNR institutional ground.

I. Source

II. Source Read

"Requirements management (RM) is performed to ensure alignment of requirements with other representations, analyses, and system artifacts generated across the life cycle." RM encompasses management of artifacts from concept definition processes (Business/Mission Analysis, Stakeholder Needs Definition) through System Definition, including understanding needs, establishing baselines, communicating requirements, managing changes, providing status, and maintaining traceability. Eight cross-cutting activities (Figure 1): managing needs and requirement definition; baselining; communicating; managing flow-down (allocation/budgeting); managing internal/external interfaces; managing bidirectional traceability; managing V&V artifacts; managing change. Configuration management and change control: baselining approved needs/requirements enables budget/schedule management; change control requires rationale documentation. Six change-driver categories: stakeholder shifts, budget/schedule changes, emerging risks, performance reallocation, operational environment changes (and a residual sixth category implicit in the page's enumeration of additional drivers). Monitoring and control metrics: number of needs/requirements, TBDs/TBRs count, untraced needs/requirements, V&V status. Requirements Management Tools (RMTs): definition, collaboration, change control, traceability, integration within digital engineering ecosystems (five capabilities, Figure 2). Traceability: links between needs/requirements and operational scenarios, risks, related requirements, V&V artifacts. RMP addresses scope, processes, responsibilities, tools, stakeholder interaction, quality assessment, change management, traceability types, hierarchy, attributes, metrics, TBR/TBD handling. Authors: Tami Katz (lead), Lou Wheatcraft, Mike Ryan. Sources: INCOSE NRM 2022, INCOSE GtNR 2022. Position: Part 3, Technical Management Processes.

III. Structural Read

Cluster A (universal-sibling lattice, Doc 572 Appendix D), with multi-rung lattice (Doc 572 D.6) sharply binding. RM operates at four nested rungs simultaneously. First rung (artifact): individual needs and requirements are sibling artifacts at the lowest rung. Second rung (process-step): the eight RM activities are sibling steps. Third rung (technical-management-process): RM is a sibling process to CM, RisM, QM, IM, Measurement at the technical-management rung. Fourth rung (life-cycle): RM operates across all life-cycle stages concurrently. The four-rung composition is the canonical Doc 572 D.6 multi-rung lattice instance: rungs nest, each rung has its own universal-sibling lattice, and the composition is the multi-rung structure itself. This is the cleanest SEBoK case of Doc 572 D.6's multi-rung sub-form and confirms the sub-form's load-bearing capacity at the technical-management-process scale.

Cluster A, three independent partitions in one article (in addition to the multi-rung composition above). First partition: eight cross-cutting activities. Universal-sibling at the activity-aspect rung. Second partition: six change-driver categories. Universal-sibling at the change-cause rung. Third partition: five RMT capabilities (definition, collaboration, change control, traceability, digital integration). Universal-sibling at the tool-capability rung. Three independent partitions plus the multi-rung composition give RM Cluster A density approaching the SE-116 three-nested-lattice density.

Cluster F (pulverization, Doc 445), bidirectional with longitudinal-pulverization (Doc 445 D) anchored at IM SE-114. RM is the engine of bidirectional pulverization across the life cycle. Forward flow-down (allocation/budgeting) pulverizes top-level needs into design constraints. Reverse change-management pulverizes change events back to affected baselines. Doc 445 D's longitudinal-pulverization anchor at IM (SE-114) binds: RM artifacts persist across life-cycle stages via the IM substrate. SE-125 confirms the anchor.

Cluster I (pin-art / temporal-concurrency, Doc 572 Appendix C). RM activities run concurrently across all life-cycle stages. The pin-art reading: each RM activity pins into every life-cycle stage simultaneously. The page's "across the life cycle" phrase names the temporal-concurrency.

Cluster B (multi-keeper composition, Doc 604), three-author keeper composition. Tami Katz (lead) plus Lou Wheatcraft plus Mike Ryan compose the article's voice; INCOSE NRM 2022 and GtNR 2022 are the institutional carriers. This is a three-author co-keepership instance. Doc 604's multi-keeper formalization composes; the keeper-side school formalization runs through INCOSE.

Cluster D (co-production at sub-rungs, Doc 573). Requirements are co-produced between stakeholders (who originate needs) and engineers (who structure them as requirements). RM is the discipline by which the co-production is maintained over time. The "stakeholder interaction" component of the RMP is the co-production rung explicitly named.

Cluster E (institutional ground, Doc 571). INCOSE NRM 2022 and GtNR 2022 are the institutional ground. Doc 571 §X.5 organization-vs-enterprise binds: NRM and GtNR live at the organization-component; RM practice lives at the enterprise-component (the working tradition INCOSE codifies).

IV. Tier-Tags

  • RM definition (alignment of requirements with other representations, analyses, and system artifacts) — π / α as cited.
  • Eight cross-cutting RM activities — π / α as cited; μ / β under Doc 572 Appendix D universal-sibling at activity-aspect rung.
  • Six change-driver categories — π / α as cited; μ / β under Doc 572 Appendix D at change-cause rung.
  • Five RMT capabilities — π / α as cited; μ / β under Doc 572 Appendix D at tool-capability rung.
  • Multi-rung RM operation (artifact / process-step / TMP / life-cycle) — μ / β under Doc 572 D.6 multi-rung lattice as canonical worked example.
  • Bidirectional traceability and flow-down — π / α as cited; μ / β under Doc 445 bidirectional pulverization.
  • Authorship (Katz, Wheatcraft, Ryan) — π / α as cited; μ / β under Doc 604 three-author co-keepership.
  • INCOSE NRM 2022 / GtNR 2022 — π / α as cited; μ / β under Doc 571 institutional ground.

V. Residuals

No structural residual. The Cluster A multi-rung lattice (Doc 572 D.6) stress-test passes sharply: RM is the canonical four-rung worked example. The sub-form's load-bearing capacity at the technical-management-process scale is confirmed.

VI. Provisional Refinements

Doc 572 D.6 multi-rung lattice sub-form confirmed with canonical worked example. RM operates at four nested rungs (artifact, process-step, TMP, life-cycle). The composition is the multi-rung structure itself. Doc 572 D.6's prediction (technical-management processes operate as multi-rung lattices) holds at canonical scale.

Cluster A density per article exceeds SE-116's three nested rungs. SE-125 has four nested rungs (the multi-rung composition) plus three independent partitions (activities, change-drivers, RMT capabilities) plus implicit metric and traceability-target lattices. Cluster A density per article continues to grow at Part 3 Technical Management Processes; the part-scale Cluster A density may exceed the part-scale density of Part 6 Quality Attributes (SE-116 territory).

Bidirectional-pulverization sub-form (Doc 445) gains canonical worked example. RM is the engine of bidirectional pulverization. Forward flow-down plus reverse change management compose the bidirectional structure. Combined with traceability (SE-122), RM is the canonical Doc 445 bidirectional worked example.

VII. Cross-Links

Form documents. Doc 572 D.6 (multi-rung lattice, RM as canonical four-rung worked example), Doc 572 Appendix D (universal-sibling, three independent partitions), Doc 445 (pulverization, bidirectional canonical worked example), Doc 445 D (longitudinal-pulverization anchored at IM), Doc 572 Appendix C (pin-art / temporal-concurrency), Doc 604 (multi-keeper composition, three-author co-keepership), Doc 573 (co-production at stakeholder-engineer rung), Doc 571 §X.5 (institutional ground, INCOSE NRM/GtNR).

Part-level reformulation. SE-006 (Part 3 — Systems Engineering and Management, Technical Management Processes).

Related distillations. SE-122 (Stakeholder Requirements Traceability, this batch). SE-124 (Technical Data Management, this batch). SE-114 (Information Management, longitudinal-pulverization anchor). SE-030 (Stakeholder Needs Definition, co-production precedent). SE-035 (Risk Management, sibling TMP). SE-116 (System Resilience, three-nested-rung Cluster A density precedent).

Adjacent SEBoK concepts (per source). Stakeholder Needs Definition, System Requirements Definition, Configuration Management, Information Management, Risk Management, Measurement, Quality Management.

Methodology refinement candidates. Doc 572 D.6 multi-rung lattice formalization with RM as canonical worked example. Doc 445 bidirectional-pulverization sub-form formalization with RM as canonical engine.

Appendix: Originating Prompt

"Apply refinements" / "Continue next knowledge base entrancement"

(SE-125 is one of the fourth-batch next-40 SEBoK distillations. Batch 1/5. Source is the Requirements Management page. Cluster A multi-rung lattice stress-test passes sharply; RM is the canonical four-rung worked example for Doc 572 D.6.)

Referenced Documents

More in framework