COEPD – Center of Excellence for Professional Development Happy Learning
Requirement Traceability Matrix
Introduction-
In the project there are many numbers of requirements i.e., Functional or Non-functional requirements. It is very important task for the business analyst to gather all the business requirements. After this, stakeholder will prioritize the requirements as which requirements has very high importance and which has less importance. The requirements prioritization is done by MoSCoW method. For each requirement it’s very important to have at least one test case or test scenario.
Definition-
Requirement Traceability Matrix is simple set of documents which is used to trace the requirements during the project. It shows the relationship between the requirements and test cases. For every requirement there should at least one test case or test scenario.
The RTM as name itself indicates, it is a document which trace the requirement and its respective test cases are fulfilled or not as per the business goal. The RTM is also known as the Cross Reference Matrix.
Example-
In below template the 5 requirements have the particular Req. Id, Req. Name and its description. The all-test cases are as per below
| Req ID | Req Name | Req Description | Design | D1 | T1 | D2 | T2 | D3 | T3 | D4 | T4 | UAT |
| FR0001 | User Registration | The all users should be able to register with valid Email ID and Password. | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES |
| FR0002 | Registration alert/notification | The users should get alert/notification after successful registration. | YES | YES | YES | |||||||
| FR0003 | User Login | The registered users only login on portal with their Email ID and password. | YES | YES | YES | YES | YES | YES | YES | YES | YES | YES |
| FR0004 | Login credentials | For Single User there should single Email Id and unique password. | YES | YES | YES | YES | YES | YES | YES | |||
| FR0005 | Strong Password | Need to make strong password with 5 alphabet (one capital), one character and 3 number. | YES | YES | YES | YES | YES |
Importance
- It helps to check all the Requirements are covered or not
- It is replication of task assign to team as it indicates which work is done or which is not.
- The RTM is useful to fulfil all Requirements as per project goal.
- It’s very helpful to complete the work in pre-determined time as there should be not any scope creep, as we can track every work done by developers and tasters.
- RTM is important for any change request as we can easily add or delete the requirements as per stakeholder’s request.
- It helps the testing team understand the testing level done for a given product.
- It allows to identify the missing functionality easily.
Types
The Requirement Traceability Matrix has basically three types as per below
- Forward traceability matrix.
In this type of matrix, the mapping is done by each requirement to the appropriate test cases.
- Backward or Reverse traceability matrix.
In Backward traceability matrix the mapping is done by test cases to each requirement.
- Bidirectional traceability matrix.
In this type of matrix, the mapping is done in both ways as its helpful to cover all requirements and its test cases also.
