COEPD – Center of Excellence for Professional Development Happy Learning
The Requirements Traceability Matrix (RTM) is a tool or a document that helps project managers establish and track the project progress. It helps monitor deliveries by providing a digital thread for each demand from the beginning to the end of the project. This guarantees that the scope and deliverables of the project are in line with the baseline.
Traceability Matrix is used in different phases of the project lifecycle, such as
- The Requirements Analysis and Specification phase
- Design Analysis and Specification phase
- Risk Analysis phase
- Source Code Analysis, Unit Testing & Integration Testing phase
- Validation – System Testing, Functional Testing phase
Industries such as Aerospace, Automobiles, Healthcare, Gaming, Information & technology, etc., that develop software, hardware or video games, employ traceability as part of their quality and compliance management systems.
It measures the accuracy of projects with the stakeholders or business’s demands while ensuring that the deliverables are defect-free.
Furthermore, RTM is relevant in traditional (waterfall) and modern (agile) project management methodologies. In the traditional waterfall approach, it helps to trace and verify requirements sequentially. In SCRUM methodology, it is used to record user stories between product and sprint backlog.
Introducing the Requirements Traceability Matrix.
The traditional solution to keeping these requirements and tests organized is a Requirements Traceability Matrix (RTM). In a nutshell, this matrix tracks a many-to-many relationship – many requirements to many tests. One test can cover multiple requirements, and one requirement can require multiple tests. Typically, the matrix shows the requirements across the top as columns and the associated tests down the side as rows. In this example there is an “X” to indicate which test cases relate to which requirements.
Requirements Traceability Matrix
Requirement Traceability Matrix are most commonly created using a spreadsheet which does well to display the many-to-many relationships.
Historically, these RTMs have most commonly been created using a spreadsheet which can adequately display the many-to-many relationships. However, the problem with spreadsheets is the maintenance they require. They can be time consuming to set up and maintain. They must be constantly updated with new information to reflect the tests performed, test results, defects identified, updated requirements, testing coverage and so on – an additional burden for an already busy team.
Types of Requirements Traceability Matrix-
There are a variety of different types of RTMs. The most common types are:
Forward Traceability – This type of RTM is used to make sure that the project progresses according to plan. It makes sure that the project has all the appropriate requirements applied to it going forward, and that each requirement is adequately tested.
Backward Traceability – This type of RTM is used to ensure that the project stays on track. It provides traceability to the original requirements to mitigate scope-creep and that unnecessary additional code, features and tests aren’t added to the project.
Bi-Directional Traceability – This RTM is a combination of both the Forward and Backward Traceability matrix. It tracks and ensures test coverage of all requirements. It is also used to determine the impact of changes in associated project requirements.
