What is a Traceability Matrix (TM)?
Definition: Traceability matrix is a one kind of document that used in the software testing to trace the requirements of an application. So, it will be help to track the project requirements by forward (Requirements to coding) and backward (Coding to Requirements) tracing method.
What is Requirements Traceability Matrix(RTM)?
Traceability Matrix in testing is also known as Requirement Traceability Matrix. RTM is designed before the test execution process start so we can cover maximum test cases from the requirements. In RTM mapping technique, we can ensure about each test cases are written for each requirement and conditions.
Importance of RTM
- Main Focus on the requirements so less chances to missed any test cases.
- Testers can go through the requirements thoroughly and design positive and negative test cases.
- Queries can be raised during the requirements and will help to develop defect free software products.
- Easiest way to track the each and every test cases by requirements traceability matrix (RTM).
Parameters of RTM
- Requirement ID
- Module
- Requirements Description
- Test Cases ID
- Test Cases Status
Requirements Traceability Matrix Template
| Requirement ID | Module | Requirements Description | Test Cases IDs | Test Cases Status |
| 001 | Registration | User is able to register with phone number and email id. | (1)- TC_01, TC_02 TC_03, TC_04 | TC_01 – Pass |
| 002 | Login | Two text fields should be displayed on login page. | (2)- TC_01, TC_02 TC_03, TC_04 TC_05 | TC_01- Pass TC_02 – Not tested |
| 003 | Home | Company logo and title should be displayed in H1 title. | (3)- TC_01, TC_02 TC_03, TC_04 | TC_01- Pass TC_02 – Pass TC_03 – Fail |
| 004 | Contact Us | Phone number field should be mandatory. | (4)- TC_01, TC_02 TC_03, TC_04 | TC_04 – Fail |
Requirements Traceability Matrix Example
A Requirements Traceability Matrix (RTM) is a document that tracks the relationship between the requirements and other project artifacts. Here’s an example of an RTM:
Assume that you are working on a software project that involves developing an e-commerce website. The requirements for the website include:
1.Users should be able to browse and search for products.
2. Users should be able to add products to their shopping cart and check out.
3.The website should accept payments using credit cards and PayPal.
4.The website should provide a customer service interface for users to submit queries and complaints.
5.The website should be accessible to users with disabilities.
Using this information, you can create an RTM that tracks the relationship between the requirements and other project artifacts, such as design documents, test cases, and code. Here’s an example of an RTM for the requirements listed above:
| Requirement | Design Document | Test Case | Code |
|---|---|---|---|
| 1 | Design A | Test Case 1 | Code A |
| 2 | Design B | Test Case 2 | Code B |
| 3 | Design C | Test Case 3 | Code C |
| 4 | Design D | Test Case 4 | Code D |
| 5 | Design E | Test Case 5 | Code E |
In this example, the RTM shows that requirement 1 is link to Design A, Test Case 1, and Code A. Similarly, requirement 2 is link to Design B, Test Case 2, and Code B. The same goes for requirements 3, 4, and 5.
The RTM helps to ensure that all requirements are cover in the design, testing, and implementation of the project. It also helps to identify any missing requirements or gaps in the project artifacts, which can be address before the software is release to the users.
Types Of Traceability Matrix
1. Forward traceability:
In forward traceability method, the main focus on the software development process to ensure about the process is going on right track. So, all the requirements mapped into forward direction.
2. Backward or reverse traceability:
In backward traceability method, do not need to increase the designing, product development or testing which is not mention in the business requirements. So, the main goal is that to check the existing project remains going on the right track. So, all the requirements mapped into the backward direction.
3. Bi-directional traceability (Forward + Backward):
Bi-directional traceability is a combination of forward and backward traceability. In this method, verify that all the test cases is cover as per the requirements. It also considers the requirements which are change due to defects in the application.
Advantages Of Requirements Traceability Matrix
- It will helpful when missed any requirements or documents
- Ensure about 100% test coverage.
- Complete document with entire execution status and all defects
- RTM will also useful for considering software test engineer’s work with follow up to reworking and revising test cases.
Conclusion
So in this way as above traceability matrix in testing will help to improve the quality of testing and also useful for maximum test coverage. If you are looking for more interesting blogs then please visit below links.
Happy Testing !