Requirements Traceability
The ability to follow relationships from needs and requirements through designs, implementation, tests, releases, and outcomes in both directions.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/requirements-traceability/
01What it means
Requirements traceability records the lineage and relationships of requirements: backward to their source and rationale, forward to solution components and verification evidence, and laterally to related requirements and designs. It is often represented with links or a traceability matrix, but the usable relationships matter more than the format.[1][2]
- Source need
- Stakeholder, regulation, research, or strategic rationale
- Related requirements
- Dependencies, conflicts, refinements, and versions
- Design decision
- How the intended behavior is shaped
- Implementation
- Components, services, configuration, or content
- Verification evidence
- Tests, inspections, analysis, or acceptance results
- Release + outcome
- Where the requirement shipped and whether value followed
Useful relationships matter more than a large matrix. Stale or semantically weak links can create false assurance, so trace only at a proportionate granularity.
02Why it matters
Traceability helps teams assess change impact, demonstrate coverage, find unsupported work, and explain why a capability exists. It is especially valuable where audits, safety, contracts, or many interconnected components make missing relationships costly.
03When to use it
Use formal traceability for regulated, safety-critical, contractual, integration-heavy, or long-lived systems. Apply selective links in ordinary product work where they support real decisions; comprehensive matrices are wasteful when nobody maintains or queries them.
04How it works
- Define which relationships and evidence are necessary for decisions or assurance.
- Give relevant needs, requirements, designs, tests, and components stable identifiers.
- Create backward, forward, and lateral links at the appropriate granularity.
- Use the links during change assessment, coverage review, verification, and release decisions.
- Detect orphaned requirements, unsupported components, broken links, and conflicting versions.
- Maintain or retire links as the product and requirements evolve.
05A practical example
A medical-device portal traces a dosage-warning requirement back to a safety need and forward to UI rules, API validation, automated tests, and release evidence. A threshold change reveals every affected component before implementation begins.
06Where it breaks
Traceability has substantial maintenance cost and stale links can mislead reviewers. Tool automation cannot judge whether a relationship is semantically correct, and exhaustive tracing can overwhelm low-risk teams without improving outcomes.
Common mistakes
- Building a complete matrix without a defined decision or assurance need.
- Linking artifacts once and never maintaining the relationships.
- Assuming linked requirements are correct or valuable.
- Tracing at such fine granularity that the system becomes unusable.
07Sources
- Understanding Requirements and DesignsInternational Institute of Business Analysis · Professional standardUnderstanding Requirements and Designs
- ISO/IEC/IEEE 29148:2018 — Requirements EngineeringInternational Organization for Standardization · International standardISO/IEC/IEEE 29148:2018 — Requirements Engineering