Requirement Traceability Matrix

Traceability Matrix:

• In this document the test cases are mapped to the corresponding requirement to ensure the coverage of test cases, to find any gap between requirement and test cases.
• It is also known as Requirement Traceability Matrix (RTM) or Cross Reference Matrix (CRM).
• It is prepared before the test execution process.
• This document is designed to make sure that each requirement has a test case. 
• The test engineer will prepare TM for their respective assign modules, and then it will be sent to the Test Lead. Then test lead consolidate all and prepare one TM document for project.

Goals of Traceability Matrix:

• It allows you to see if a requirement is fully documented or not. A requirement traceability matrix can even call attention to missing requirements. 
• It ensures that the software completely meets the customer's requirements.
• A traceability matrix can help in the effort to provide proper and consistent documentation for your team. 
• It helps in detecting the root cause of any bug.

Types of Traceability Matrix:

The traceability matrix can be classified into three different types which are as follows:  

• Forward Traceability
• Backward or reverse Traceability
• Bi-directional Traceability

Forward Traceability:

Forward traceability is used to map the requirements to the test cases.

• Not only this will establish that every requirement is being tested from top to bottom, but it will also assist in confirming that a project’s trajectory is sound. 
• The main objective of this is to verify whether the product developments are going in the right direction.

Backward or reverse Traceability:

You can make a backward traceability matrix by mapping test cases with the requirements. 

• The reverse or backward traceability is used to check that we are not increasing the space of the product by enhancing the design elements, code, test other things which are not mentioned in the business needs. 
• The main objective of this that the existing project remains in the correct direction.

Bi-directional Traceability:

Bidirectional traceability essentially combines forward and backward traceability into one document. 

• This type is useful because it establishes that each requirement has relating test cases. 
• It also evaluates the modification in the requirement which is occurring due to the bugs in the application.