COEPD – Center of Excellence for Professional Development Happy Learning
PURPOSE OF REQUIREMENT TRACEABILITY MATRIX
The Requirement traceability matrix is a software which is used to validate the requirements given by the client. This document validation is done mainly to check whether all the project purpose are met in current state.
The important stage of all testers should make sure the client requirements are tested bug-free. Traceability matrix can be divided into two parts, the test scenario and the test cases. In this, worksheet which contains all the detailed descriptions of the test scenarios corresponding to the test cases , which checking whether its passed or failed.
Requirement traceability matrix has three types to process the documents.
Forward Traceability is first method which is used to check the entire project is travelling towards the right product until its achieved. It will test the entire test cases of the product to make sure its met client requirements.
Backward Traceability is another method to test the current state of the product in right path to achieve the next phase. It also look for there is out of scope of the requirement , design or testing . it should be right to the requirements
Bi-Directional traceability is combination of both the forward and backward matrix. It cross verify all the requirements are tested to the product or the changes in requirements to get defect free product , vice versa.
To a make better document for the testers to achieve a product, the following components are described for the Traceability Matrix.
- Lets start on the basis business requirement documents. This should have requirement numbers, followed by module name , applicable roles then the descriptions.
| BR | module name | descriptions |
| Br001 | Login Page | A end user should able to login into home page successfully |
- Then should write the technical requirement documents, for example it has the login module descriptions.
- Then comes the RTM, the test case contains the test cases numbers, test case, test case steps, test data, test expected results.
| Test case no | Test case | Test case steps | test data | Result |
| T001 | Login Page | create login page enter id and pwd click enter |
id= hd001991 | passed |
- Now, test the technical requirement matrix , to check whether the login page has passed the condition or not, document the expected result.
- Documents the test results in the RTM document.
- Verify the business requirements documents against the requirement traceability matrix to make sure the project goal is achieved.
| BR | Test case no | module name | module name | Test case steps | test data | descriptions | Expected result |
| Br001 | T001 | Login Page | Login Page | create login page enter id and pwd click enter |
id= hd001991 | A end user should able to login into home page successfully | Successfully login |
The pros the traceability matrix:
- All the test cases are tested completed
- Make sure all the test cases are tested defects-free for right product.
- It aids the quality team to check the entire project direct crystal clear.
- All the business requirements are covered and delivered the expected results to the clients.
- It also helps to identify all the requirements are processed without missing for future references.
