# Requirements Traceability

The ability to follow relationships from needs and requirements through designs, implementation, tests, releases, and outcomes in both directions.

- Type: practice
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/requirements-traceability/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Define which relationships and evidence are necessary for decisions or assurance.
2. Give relevant needs, requirements, designs, tests, and components stable identifiers.
3. Create backward, forward, and lateral links at the appropriate granularity.
4. Use the links during change assessment, coverage review, verification, and release decisions.
5. Detect orphaned requirements, unsupported components, broken links, and conflicting versions.
6. Maintain or retire links as the product and requirements evolve.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/requirements-traceability/#visualization-requirements-traceability>)

## Sources

1. [Understanding Requirements and Designs](<https://www.iiba.org/knowledgehub/the-business-analysis-standard/4-implementing-business-analysis/4-4-understanding-requirements-and-designs/>) — International Institute of Business Analysis · Professional standard
2. [ISO/IEC/IEEE 29148:2018 — Requirements Engineering](<https://www.iso.org/standard/72089.html>) — International Organization for Standardization · International standard

## Related topics

- [Requirements Management](<https://wiki.soroush.uk/topic/requirements-management/>)
- [Change Control](<https://wiki.soroush.uk/topic/change-control/>)
- [Acceptance Criteria](<https://wiki.soroush.uk/topic/acceptance-criteria/>)
