Requirements Decomposition
Decompose a stakeholder need into system and subsystem requirements while preserving intent, allocation, verifiability and traceability.
Translate stakeholder intent into lower-level requirements without losing the reason the requirement exists.
Requirements decomposition transforms higher-level needs and system requirements into lower-level requirements that can be allocated, designed and verified. Good decomposition preserves intent while making each requirement sufficiently specific and testable.
This builder works from a fictional operational need through system requirements, functional and performance decomposition, subsystem allocation and a quality review. It distinguishes decomposition from simply rewriting the same sentence at several levels.
Requirements Decomposition — Step by Step
Eight stages reveal a stakeholder need, select system requirements, decompose functional and performance content, allocate to subsystems, review requirement quality, apply a changed-need challenge and conclude with management review.
Requirement Hierarchy, Allocation and Quality
Reveal the context to begin.
Review hierarchy level, requirement intent, allocation, parent trace and quality status.
Explore Decomposition Quality
Adjust decomposition coverage, allocation clarity, verifiability and change sensitivity without changing the guided requirement tree.
Test your systems-engineering judgement.
Requirements decomposition cues
Stakeholder Need
A statement of required capability or outcome from the stakeholder perspective.
System Requirement
A necessary system-level obligation derived from needs, constraints and higher-level requirements.
Lower-Level Requirement
A decomposed requirement allocated to a subsystem, component, function or enabling element.
Allocation
Assignment of responsibility for satisfying a requirement to the appropriate architecture element.
Verifiability
The extent to which objective evidence can demonstrate that the requirement has been satisfied.
Traceability
The maintained relationship from lower-level requirement back to its source and forward to verification evidence.
Decomposition is successful when lower-level requirements add actionable detail without breaking traceability to stakeholder intent.
Preserve the parent rationale, avoid unnecessary design prescription, allocate responsibility clearly and ensure each requirement can be verified.