I have newly changed my company on manual testing role and my manager asked me to make trace-ability matrix for the requirements or test cases (I am not sure). However, this is the first time I am hearing about this word 'trace-ability matrix'. However, on some blogs based on the info provided, I understood it is similar like writing business scenario, test scenario and test cases. Is my understanding correct.?
What is a Traceability Matrix?
It is used to track the requirements and to check the current project requirements are met. That is, a traceability matrix is a document that co-relates any two-baseline documents that require a many-to-many relationship to check the completeness of the relationship.
Requirement Trace-ability Matrix
Requirement Trace-ability Matrix or RTM captures all requirements proposed by the client or development team and their trace-ability in a single document delivered at the conclusion of the life-cycle.
In simple words, it is a document that maps and traces user requirement with test cases. The main purpose of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality should miss while testing.
RTM Parameter includes:
Requirement ID
Risks
Requirement Type and Description
Trace to design specification
Unit test cases
Integration test cases
System test cases
User acceptance test cases
Trace to test script
There are three types of Traceability Matrix as per my knowledge
Forward traceability
Backward or reverse traceability
Bi-directional traceability ( Forward+Backward)
Forward traceability: This matrix is used to check whether the project progresses in the desired direction and for the right product. It makes sure that each requirement is applied to the product and that each requirement is tested thoroughly. It maps requirements to test cases.
Backward or reverse traceability: It is used to ensure whether the current product remains on the right track. The purpose behind this type of traceability is to verify that we are not expanding the scope of the project by adding code, design elements, test or other work that is not specified in the requirements. It maps test cases to requirements.
Bi-directional traceability ( Forward+Backward): This traceability metrics ensures that all requirements are covered by test cases. It analyzes the impact of a change in requirements affected by the defect in a work product and vice versa.
Advantage of Requirement Traceability Matrix
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 analyzing or estimating the impact on the QA team's work with respect to revisiting or re-working on the test cases