Requirement Traceability Matrix:
The Requirements Traceability Matrix (RTM) is a document that helps the project manager to check the project progress. It is a kind of document that defines multiple relationships between use cases (requirements) and test cases. It is used to ensure that the requirements defined are linked at every point during the verification process. This assures that the scope and its deliverables of a project is in line with the baseline.
Purpose of RTM:
The main purpose of Requirement Traceability Matrix is to validate that all requirements are checked with each test cases such that it signifies no functionality remains unchecked.
Importance of RTM in a Project:
- Helps in Tracking the requirements of each sprint, release and project can be difficult especially in fast paced development environments. Depending on the organization, an application each release sprint can have a wide variety of requirements.
- Addition to this, the managers can accurately estimate the resource requirements based on project activities & initiate the requirement process.
- The resource manager also identifies and assign the best suitable resources for successful project delivery.
- During the validation process, the RTM will display multiple different test scenarios, test case status for various functionalities for the project.
- The Requirements Traceability Matrix (RTM) reduces the risk of defects and missed objectives. It helps project managers to evaluate and identify risks before they become issues in a project.
Types of RTM:
There are three key types of requirement traceability matrices used in requirements tracing, as mentioned below:
- Forward Traceability Matrix: FTM maps requirements to every test cases. This matrix is used to check the current progress of the project that is it going in the desired direction and for the right product. It makes sure that each requirement is applied to the product and thereby each & every requirement is tested thoroughly.
- Backward or Reverse Traceability Matrix: BTM is used to check whether the current product remains on the right track or not then measures are taken. The purpose behind this type of traceability is to verify that the team is not expanding the scope of the project by adding code, design elements, test or other work that is not specified in the requirements.
- Bi-Directional Traceability Matrix: BDT matrix is termed bi-directional when it tracks the requirement “FTM” by looking at the output of the deliverables and “BTM” by examining the requirement specified in the project initiation It allows the project team to have complete visibility into specifications through building, testing, tracking changes, analyzing defects, etc. hence is considered as Bi- Directional Matrix.
How to create RTM:
- Start with defining your RTM goals by laying out the appropriate reason for creating the “Requirement Traceability Matrix” as per client’s need.
- Gather all accessible requirement documentation, such as the technical requirements documentation (TRD) or functional requirements documentation (FRD), and business requirements documentation (BRD). Then the testing documentation, like test cases, results, and bugs will be required to perform RTM.
- To make a simple RTM document, the Excel spreadsheet is used. Columns should be created in excel spreadsheet for business requirements, functional requirements, test cases, test results, and bugs. Then, record each requirement from BRD with a requirement ID number, for e.g. (FR001, BR0001).
- Take the FRD in use and record all corresponding functional requirements for every business requirement.
- Connect test case IDs with the required functional requirements.
- Now, always remember to update your traceability matrix with the end users when a change occurs or for further updating if required.