Requirement Traceability Matrix (RTM) is a document that maps and traces user needed thing with test cases. It takes by force/takes control of all needed things proposed by the client and needed thing traceability in a single document, delivered at the end of/final opinion of the Software development life cycle. The main purpose of needed thing Traceability Matrix is to validate that all needed things are checked via test cases such that no ability to do things is unchecked during Software testing.
The main (list of things to deal with/desire to reach a goal) of every tester should be to understand the client’s needed thing and make sure that the output product should be defect-free. To (accomplish or gain with effort) this goal, every QA should understand the needed thing completely and create positive and negative test cases.
This would mean that the software needed things given by the client have to be further split into different pictures/situations and further to test cases. Each of this case has to be executed individually.
A question rises/comes up here on how to make sure that the needed thing is tested (thinking about/when one thinks about) all possible pictures/situations/cases? How to make sure that any needed thing is not left out of the testing cycle?
A simple way is to trace the needed thing with its corresponding test pictures/situations and test cases. This only is termed as ‘Requirement Traceability Matrix.’
The traceability matrix is usually a worksheet that contains the needed things with its all possible test pictures/situations and cases and their current state, (in other words) if they have been passed or failed. This would help the testing team to understand the level of testing activities done for the clearly stated/particular product.
RTM Matrix Contain
- Requirement ID
- Requirement Type and Description
- Test Cases with Status
Types of Traceability Test Matrix
In Software Engineering, traceability matrix can be divided into three major component as mentioned below:
Forward traceability: This matrix is used to check whether the project goes forward in the desired direction and for the right product. It makes sure that each needed thing is applied to the product and that each needed thing is tested completely. It maps needed things to test cases.
Backward or reverse traceability: It is used to secure/make sure of whether the current product remains on the right track. The purpose behind this type of traceability is to (check for truth/prove true) that we are not expanding the extent of/the range of the project by adding code, design elements, test or other work that is not specified in the needed things. It maps test cases to needed things.
Bi-directional traceability ( Forward+Backward): This traceability matrix secures/makes sure of that all needed things are covered by test cases. It carefully studies the hit/effect of a change in needed things affected by the Defect in a work product and the other way around, too