Glossary · System coordination, integration and orchestration
Traceability matrix
Also known as: Requirements traceability matrix (RTM)
German: Rückverfolgbarkeitsmatrix
In systems and software engineering, a traceability matrix is a table or report that shows the relationships between artifacts, typically requirements and the design elements, implementation, tests and evidence that address them, so that coverage and the impact of changes can be checked.
- System integration
- Technical documentation
In one sentence
A traceability matrix shows which design elements, tests and evidence address each requirement, making coverage and change impact visible.
Example
The traceability matrix of a safety function links each safety requirement to the PLC program module that implements it, the validation test that checks it and the test report.
How it applies
- Engineering: A traceability matrix is usually generated from Trace links held in requirements or ALM tools, rather than maintained by hand. Gaps (requirements without tests, tests without requirements) become visible at a glance.
- Safety and regulation: Functional safety standards and regulated industries expect traceability from requirements to verification and validation. The matrix supports the argument but does not by itself demonstrate that the requirements are met.
- Change: When a requirement changes, the matrix shows affected design elements and tests for Impact analysis.
- Documentation: Documentation can be traced too: link requirements allocated to users (warnings, procedures, residual risks) to the sections of the instructions that fulfill them. This lets technical writers show that every required piece of safety information is present.
Traceability matrix vs. responsibility matrix
A traceability matrix relates artifacts to each other. A Responsibility matrix relates tasks to people or organizations. Both are tables with different purposes.