STLC - What is Requirement Traceability Matrix

What is the Requirement Traceability Matrix?

Requirement Traceability Matrix is a document prepared by the test manager to map the requirements listed by the client to that of test cases that would run against them. It is a many-to-many document prepared on an excel sheet. It indicates the extent of testing on every functionality to ensure quality in time and budget constraints.

Why is Requirement Traceability Important?

1. RTM acts as a tracker to know which functionalities have been tested and which are pending for both the development and testing teams.
2. Preparing RTM is crucial for the next step in STLC, test planning. Based on RTM, the entire test architecture is laid down.
3. RTM contains the current states of test cases, i.e., which have been passed, failed, and pending.
4. RTM ensures all functionalities have been tested and nothing is left. Updating this document ensures that.

Parameters to Include in Requirement Traceability Matrix

Following are the pointers that are mentioned in the RTM.

1. Information about Requirement, i.e., Req Id, Req Description,
2. Test case mapping Test Scenario, Test Case Id, Test Case Description, and Test status. Only mapping of test cases is done here.
3. Defects are also mapped using Defect Id and Defect status.
4. Lastly, the Requirement Coverage status is mentioned here. The terminology here is Partial, Complete, and None.

Types of Traceability Test Matrix

A traceability test matrix can be created for three primary purposes:

• Forward traceability: This ensures that all requirements have been mapped to test cases in RTM. That is, test case coverage is the primary concern. It keeps track of test cases, what is the current status, and if there are any bugs.
• Backward or reverse traceability: RTM can also be used to ensure no unnecessary code. All test cases have been covered, and the requirement is satisfied, but the developer has added more cases. Then that aspect can also be a useful feature in reverse traceability.
• Bi-directional traceability: RTM document created to ensure all test cases are covered and no unnecessary code added to ensure the SDLC cycle is going in the correct path is bi-directional traceability.

Creating a Requirement Traceability Matrix

Step 1: Map the Requirements in an excel document. There is already a separate document for a requirement where the absolute requirement is listed in detail. Here we require only the reqId, and req Desc because RTM is a mapping document.

Step 2: Map the test cases to requirements. Again, only the test case is attached to the requirement. We don't write detailed test case columns like steps, expected results, etc. Here, we map testcaseId, test case status

Step 3: Map defects to the test cases. Here, we specify defect Id and defect status. The only objective here is to know the defect's status to that of the requirement to keep a tracker.

Step 4: Requirement coverage status is updated after test planning is done. It is further updated after the test execution stage.

Advantage of Requirement Traceability Matrix

1. It ensures the maximum test coverage possible.
2. It acts as a tracker for the testing team. The status of test execution and bugs.
3. RTM also keeps a tracker for bug management. Bugs are pending, and hence, keep the development team involved.
4. RTM is necessary to ensure the development cycle is on track and helps minimize time and effort where ever possible.