Traceability Matrix is a set of rules to trace the deliverable to the requirement and vice versa.

Traceability Matrix is used to

  • verify and validate system specifications,
  • ensure that all final deliverable documents are included in the system specification, such as process models and data models,
  • Improve the quality of a system by identifying requirements that are not addressed by configuration items during design and code reviews and by identifying extra configuration items that are not required. Examples of configuration items are software modules and hardware devices,
  • provide input to change requests and future project plans when missing requirements are identified,
  • Provide a guide for system and acceptance test plans of what needs to be tested.



Taking the time to cross-reference each requirement to a deliverable ensures that a deliverable is consistent with the customer and system requirements. A requirement that cannot be mapped to a deliverable is an indication that something is missing from the deliverable. Likewise, a deliverable that cannot be traced back to a requirement may mean the system is delivering more than required.

Useful traceability matrices examples:

  • Functional specification to requirements document: It shows that each requirement (obtained from a preliminary requirements statement provided by the customer or produced in the Concept Definition stage) has been covered in an appropriate section of the functional specification.
  • Design specification to functional specification verifies that each function has been covered in the design.
  • System test plan to functional specification ensures you have identified a test case or test scenario for each process and each requirement in the functional specification.




Although the construction and maintenance of traceability matrices may be time-consuming, they are a quick reference during verification and validation tasks.