What it means
A traceability chain shows why a requirement exists, where it is implemented, how it is verified, who owns it, and what must change when assumptions or system components change.
Why it matters
Traceability reduces silent gaps and contradictory decisions. It also helps teams demonstrate that important requirements survived design, implementation, testing, deployment, and later change.
Practical focus
- Assign stable identifiers to requirements and evidence
- Trace requirements in both directions
- Record rationale, source, owner, and verification method
- Update links when risk, design, or implementation changes
Common mistakes
- Maintaining a spreadsheet that no one uses
- Tracing controls without tracing the underlying need
- Allowing many-to-many relationships to become ambiguous
- Treating successful testing as permanent proof
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: