Why is Requirements Traceability Matrix (RTM) required?

A Requirements Traceability Matrix (RTM) helps you answer the following questions:

  1. What are the test cases written for requirement X?

    Answering this question will help you ensure that test cases have been written for all requirements. If any requirement changes in the future, you would easily know the test cases that needs to be revised.

  2. What requirement is associated with test case Y?

    Answering this question enables you to check the correctness and comprehensiveness of a test case based on the requirement.

What is a requirements traceability matrix (RTM)?

A requirements traceability matrix (RTM) is a document that describes the relationship between customer requirements and test artifacts, especially test cases. The primary purpose of an RTM is to ensure that there are test cases for all requirements.

Every industry that develops software or manufactures hardware can use requirement traceability. But it's essential for quality and safety-critical enterprises to prove compliance.

There is no standard format of RTM; every organization uses its own. However, no matter which form you use, you ensure that it has bidirectional traceability. Bidirectional traceability is the ability to trace forward (e.g., from a requirement to its test cases) and backward (e.g., from a test case to its requirement).

Here is a real-world example of a RTM:

As you can see, you can trace the test cases based on requirements and vice-versa. For example, you can see that test cases for the ability to reset password has not yet been written.

746  people found this useful