Requirement Traceability Matrix
What is RTM (Requirement Traceability Matrix)
RTM is made up of 4 words.
Requirement + Trace + Ability + Matrix
It is a Matrix (Document) where we should be able to trace each and every requirement
So, How do we trace each and every requirement.
We map all the test cases and test scenarios to the related requirement in this Document
It’s a Document where Test Cases, Test Scenarios and Requirements are linked or mapped to each other.
We divide each requirement into different Test Scenarios and then into different Test Cases.
- Requirement 1
- Test Scenario 1
- Test Case 1
- Test Case 2
- Test Scenario 1
- Requirement 2
- Test Scenario 2
- Test Case 3
- Test Case 4
- Test Scenario 2
Why RTM was introduced
Importance of RTM
Whenever we plan a project, then it is very important that each and every requirement is developed and tested, So that we don’t miss any requirement. So we make sure that we create Test Case for each and every requirement and execute them.
Our main agenda is at the end, to deliver the quality product to the end user or we can say, to deliver a defect free product to end user. So, If we make sure that we have created test case for each and every requirement and then we have executed the test cases and found them passed, then we can say, that we have delivered a quality product or a defect free product to the end user.
The Biggest Question that always comes to mind , that how do we make sure that each and every requirement has been tested and the answer to that is Requirement Traceability Matrix (RTM).
How does RTM look like
Format of RTM
It is basically a spreadsheet, which has following columns
- Requirement ID
- Requirement Description
- Test Scenario
- Test Cases
- Test Status
- Defect
Requirement ID | Requirement Description | Test Scenario | Test Cases | Test Status | Defect |
|
Example of RTM
Let’s take an example of a Project, where we have to do Software testing for an eCommerce Website. So, we will have some requirements in that project, and we will write test scenarios and test cases for those requirements, Now if we want to make sure that we have covered all the requirement, then we have to trace the requirements in RTM, So We will create an RTM and it will look like this.
Requirement ID | Requirement Description | Test Scenario | Test Cases | Test Status | Defect |
1 | Create Account or Register Functionality | Test the Create Account Functionality with email ID and Mobile No. | Test the Create Account Functionality with email ID | Passed | |
Test the Create Account Functionality with Mobile No. | Failed | 123 | |||
2 | Login Functionality | Test Login functionality for valid and invalid credentials | Test Login functionality for valid user name and valid password | Passed | |
Test Login functionality for valid user name and invalid password | Passed | ||||
Test Login functionality for invalid user name and valid password | Passed | ||||
Test Login functionality for invalid user name and invalid password | Failed | 124 |
How does RTM Help
- We make sure that we have written test scenarios and test cases for each Requirement. So RTM helps in 100% coverage.
- If any defect comes then we can find out that which area is being affected because of a defect and then we can test those test cases and we don’t need to test all the test cases which saves our time.
- We can identify that majority of the defects have come from which area and we can make sure that which functionality gives us more defect. Generally 80:20 principle works here, i.e. 80% defect comes from 20% functionalities.
Summary
We have covered below topics today
- What is RTM (Requirement Traceability Matrix)
- Importance of RTM (Requirement Traceability Matrix)
- Format of RTM (Requirement Traceability Matrix)
- Example of RTM (Requirement Traceability Matrix)
- How does RTM help
Question
What is the purpose of a requirement traceability matrix (RTM) in software development, and how is it used to measure project success?