Requirement Traceability Matrix (RTM) is created to track the components through each level of its development for ensuring the completeness and its validation at each step. It is created as a table in excel sheets to establish trace for requirements.
This document should cover all the product requirements whether those are provided by customers or developers. The most imporant step for creating RTM is identification of artifacts (Customer Requirements, Software, Internal Requirements (System, hardware, legal requirements, etc.), Software architecture, Implementation and Test Cases ).
In QA testing companies, it is created to satisfy the 100% testing coverage. Below are the steps to create traceability matrix:
- Create a spreadsheet (excel sheet) with below columns:
- Requirement ID
- Requirement description
- Test Scenario ID
- Test Case ID
- Status
- Defects
- Analyze and capture the detailed requirements:
- Use Cases
- Business logics
- Functional logics
- Validation/Error Messages
- Product requirement specifications
- Functional requirement specifications
- Analysze and prepare the test scenarios to be covered.
- Link the Requirement ID with test case.
Please refer below sample RTM table:
Requirement ID
|
Requirement Description
|
Test Scenario ID
|
Test Case ID
|
Status
|
Defects
|
SR 1.1
|
Login/Logout
|
TS 001: Validate that the user is able to input username.
|
TC_login001
|
Pass
|
|
|
|
TS 002: Validate that the user is able to
|
TC_login002
|
Fail
|
Defect_001,
Defect_002
|
|
|
TS005: XXXXXXXXXXX
|
TC_login005
|
Pass
|
|
SR 1.2
|
Existing Users
|
TS 006: XXXXXXX
|
TC_User001
|
Pass
|
|
|
|
TS 0010: XXXXXXXXX
|
|
Fail
|
Defect_003, Defect_004
|
You can also add additional fiels to the spreadsheet as per your project requirement. For example:
- Technical Assumptions
- Customer Requirements
- Functional Requirement
- Status
- Design Document
- Technical Specification
- System Components
- Product Module
- Tested In Build
- Implemented In Build