Requirements Traceability Matrix (RTM)
A document showing the relationship/mapping between Test Requirements and Test Cases.
(RTM) captures the complete user and system requirements for the system, or a portion of the system. The RTM captures all requirements and their traceability in a single document, and is a mandatory deliverable at the conclusion of the lifecycle.
The RTM is used to record the relationship of the requirements to the design, development, testing and release of the software as the requirements are allocated to a specific release of the software. Changes to the requirements are also recorded and tracked in the RTM.
The RTM Template shows the Mapping between the actual Requirement and User Requirement/System Requirement.
Any changes that happens after the system has been built we can trace the impact of the change on the Application through RTM Matrix.
- Requirement ID
2. Risks
3. Requirement Type (User or System)
4. Requirement Description
5. Trace to User Requirement/Trace From System Requirement
6. Trace to Design Specification
7. UT * Unit Test Cases
8. IT * Integration Test Cases
9. ST * System Test Cases
10. UAT * User Acceptance Test Cases
11. Trace to Test Script
The following is the sample Template of Requirements Traceability Matrix.
| Requirement ID | Risks | Requirement Type | Requirement Description | Trace to User Requirement/Trace(From System Requirement) | Trace to Design Specification | UT | IT | ST | UAT | Trace to Test Script |
Verification and Validation (VandV)
Verification is testing that your product meets the specifications / requirements you have written. “Did I build what I said I would?”
Validation tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. “Did I build what I need?”
Difference between Verification and Validation:
Suppose, you are going to buy a pair of bangles having size 2/4 for you. You have chosen a pair and seen the tag with 2/2 written on it. This is verification, because your requirement was to buy a pair of bangles with 2/4size.
But when you tried to wear it and found that bangle is not fitted into your hand. After inquiry, you have found that company has tagged it 2/4 size by mistake. Actually it was 2/2 size bangles. This process is called Validation.
Example of Verification: Creating Traceability Matrix
Example of Validation: Executing Test Cases