Home / BA / 2. What is the purpose of the Requirement Traceability Matrix?

2. What is the purpose of the Requirement Traceability Matrix?

Requirement traceability Matrix is a document which shows the relationship between work done and other artifacts. It manages the project requirement overall. There are many kinds of RTM.

The main agenda of the tester is to understand the client’s requirement and get a defect free product. To achieve this goal tester need to understand the requirement and have a test get both positive and negative test case. The requirement traceability matrix includes requirement, test case, test result and issues.

Create Template of Requirement traceability matrix – First we need to define a goal, then gathering artifacts is important.

How to create a traceability matrix- Need to copy paste the required documents, then copy the test case from the test case document, Copy paste the test result and issues. Finally update the traceability matrix regularly.

A simple way to trace the requirement with its corresponding test scenario and test cases. This is called Requirement Traceability matrix.


  • Requirement ID is one of the parameters of RTM as it gives and listing number.
  • Requirement Type and Description is required for RTM is by grouping or categorising the requirement.
  • Test Cases with Status is important for RTM


  • Get visibility across development There is clarity of the development of the project while tracking the RTM.
  • Make better decisions (e.g., on requirements change) RTM is required for making better decision as it shows the changes of requirement.
  • Accelerate release cycles- It increases the pace of the project.
  • Rest easy knowing your requirements are fulfilled. Due to RTM it’s easy for tracking of the projects and knows which requirement is fulfilled.
  • Prove compliance faster- It shows the improvement of the compliance.
  • Pass audits without fear- It passes the audit as due to proper tracking and continuous monitor.

Advantage of RTM

  • It confirms 100% test coverage
  • It highlights any requirements missing or document inconsistencies
  • It shows the overall defects or execution status with a focus on business requirements
  • It helps in analysing or estimating the impact on the QA team’s work with respect to revisiting or re-working on the test cases

Different Types of RTM-

Forward Traceability- 

This document is used to map the requirement to the test case. This will ensure the right movement of projects.

Backward Traceability-

This document is used to map the scope of project to its functionality. It should not be added to additional features.

Bidirectional Traceability-

When you are mapping the requirement to test case for forward traceability and test case to requirement for Backward traceability in a single document it called Bidirectional traceability.

How to create RTM-

  • Set Goals- It sets the goal for completion of the projects.
  • Collect artifacts- It collects the artifacts for completion of the project
  • Prepare traceability template- It prepares the traceability template to trace the completion of the project.
  • Adding the artifacts- Adding of the artifacts to complete the project.
  • Update the traceability matrix- Update the traceable matrix regularly to see the completion of project.

Conclusion- The requirement traceability matrix is used to track the as how the project was processing in each phase. It meets the expectation of stakeholder. The above mentioned information show the importance and definition of RTM. It also shows the benefits of RTM as well as how it is created.

About Sarada Dash

Check Also

Q2. What are project priorities? Why this is important? How to handle this?

Project prioritization is the process of determining which projects are the most important and the …

Leave a Reply

Watch Dragon ball super