Requirements Traceability Matrix

Definition

Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability, its forward traceability, and its relationship to other requirements. Traceability is used to help ensure that the solution conforms to requirements and to assist in scope, change, risk, time, cost, and communication management.

Inputs

• A documented set of requirements (business, stakeholder, solution, or transition)
• Source artifacts the requirements originated from (business case, stakeholder requests, regulatory documents)
• Design and solution components the requirements will map forward to

Outputs

• A matrix or table linking each requirement to its origin, related requirements, and downstream design/solution elements
• Visibility into orphaned requirements (no source) and orphaned design elements (no requirement)

When to Use

• Regulated or compliance-driven projects where audit trails are required
• Projects with many stakeholders or complex dependencies, where change impact needs to be assessed quickly
• Any project where "why does this requirement exist" or "what does this requirement affect" needs a fast, reliable answer

When Not to Use

• Very small, short-lived projects where the overhead of maintaining a matrix exceeds its value
• Early-stage discovery work where requirements are still highly fluid and traceability would need constant rework