Requirements Traceability
Link stakeholder needs, system requirements, subsystem requirements and verification evidence to expose coverage, gaps and change impact.
Turn a list of requirements into an evidence chain that can support coverage and change control.
Traceability connects requirements to their sources, decomposition, allocation and verification evidence. Bidirectional traceability helps teams answer why a requirement exists, what depends on it and whether satisfaction is demonstrated.
This tool builds a small end-to-end trace chain, then tests coverage, verification evidence and change impact. The goal is not to maximise links; it is to create meaningful trace relationships that support engineering decisions.
Requirements Traceability — Step by Step
Eight stages establish the requirement set, build upstream and downstream traces, connect verification evidence, assess coverage, apply a changed-need challenge and conclude with management review.
Need-to-Evidence Trace Chain and Coverage Matrix
Reveal the context to begin.
Review trace links, coverage, verification status and change-impact exposure.
Explore Traceability Health
Adjust upstream coverage, downstream coverage, evidence completeness and change volatility without changing the guided trace network.
Test your systems-engineering judgement.
Requirements traceability cues
Upstream Trace
Links a requirement back to the higher-level need, requirement, rationale or source that justifies it.
Downstream Trace
Links a requirement forward to lower-level requirements, design elements, verification cases or evidence.
Orphan Requirement
A requirement with no valid upstream source or rationale.
Unverified Requirement
A requirement lacking planned or completed verification evidence.
Coverage
The proportion of required trace relationships that are present and meaningful.
Change Impact
The set of requirements, design elements, verification cases and evidence potentially affected by a source change.
Traceability creates value when it answers why, where, how and with what evidence—not when it merely increases link count.
Use trace links to expose gaps, support verification planning and understand change propagation across the requirement hierarchy.