---
title: What is Requirement Traceability Matrix (RTM) ? 
description: "**What is Requirement Traceability Matrix** **(RTM) ? ** The **Requirement Traceability Matrix (RTM)** is a document used in software testing to ensure that all requirements are covered by test cases. It establishes a clear link between requirements, test cases, and defects,…"
url: "https://vinothqaacademy.com/docs/what-is-requirement-traceability-matrix-rtm/"
updated: "2025-02-05"
category: QA Software Testing
tags:
  - QA Software Testing
---

# What is Requirement Traceability Matrix (RTM) ? 

**What is Requirement Traceability Matrix**

**(RTM) ? **

The **Requirement Traceability Matrix (RTM)** is a document used in software testing to ensure that all requirements are covered by test cases. It establishes a clear link between requirements, test cases, and defects, ensuring that every requirement is tested and tracked throughout the software development lifecycle. RTM is a critical tool for maintaining transparency, ensuring test coverage, and managing changes in requirements.

***Purpose of RTM***

1. **Ensure Coverage**: Verify that all requirements are mapped to test cases.
2. **Track Progress**: Monitor the status of testing for each requirement.
3. **Manage Changes**: Handle changes in requirements and assess their impact on testing.
4. **Improve Quality**: Identify gaps in testing and ensure no requirement is left untested.

How to Prepare a Requirement Traceability Matrix (RTM)?

Preparing a **Requirement Traceability Matrix (RTM)** involves systematically mapping requirements to test cases and tracking their status throughout the testing process. Below is a step-by-step guide to creating an RTM:

***Steps to Prepare an RTM***

***1. Gather Requirements***

- Collect all requirements from documents such as:
  - Business Requirement Specification (BRS)
  - Software Requirement Specification (SRS)
  - Functional Requirement Specification (FRS)
- Ensure the requirements are clear, complete, and well-defined.

***2. Assign Unique Requirement IDs***

- Assign a unique identifier (ID) to each requirement for easy reference.
- Example: REQ-001, REQ-002, etc.

***3. Identify Test Cases***

- Create test cases that validate each requirement.
- Assign unique IDs to test cases.
- Example: TC-001, TC-002, etc.

***4. Map Requirements to Test Cases***

- Link each requirement to one or more test cases.
- Ensure all requirements are covered by at least one test case.

***5. Define Test Case Descriptions***

- Provide a brief description of each test case.
- Example: "Verify login with valid credentials."

***6. Add Columns for Status and Defects***

- Include columns to track:
  - **Status**: Pass, Fail, Not Executed, Blocked, etc.
  - **Defect ID**: If a test case fails, log the defect ID.
  - **Comments**: Additional notes or observations.

***7. Populate the RTM***

- Fill in the RTM with the requirement IDs, test case IDs, descriptions, and other details.
- Update the status and defect information as testing progresses.

***8. Review and Validate***

- Review the RTM to ensure:
  - All requirements are mapped to test cases.
  - There are no gaps or missing test cases.
  - The RTM is accurate and up-to-date.

***9. Maintain the RTM***

- Update the RTM regularly as requirements change, new test cases are added, or defects are resolved.
- Use the RTM to track progress and ensure complete test coverage.

*Template for RTM*

*Here’s a sample RTM template:*

| **Requirement ID** | **Requirement Description** | **Test Case ID** | **Test Case Description** | **Status** | **Defect ID** | **Comments** |
| --- | --- | --- | --- | --- | --- | --- |
| REQ-001 | User should be able to log in with valid credentials. | TC-001 | Verify login with valid email and password. | Pass | - | - |
| REQ-001 | User should be able to log in with valid credentials. | TC-002 | Verify login with invalid password. | Fail | DEF-001 | Error message not displayed. |
| REQ-002 | User should not be able to log in with invalid email. | TC-003 | Verify login with non-existent email. | Pass | - | - |
| REQ-003 | System should display an error message for invalid inputs. | TC-004 | Verify error message for invalid email. | Not Executed | - | Pending due to environment issues. |

***Example Scenario***

Suppose you are testing a login feature with the following requirements:

1. **REQ-001**: User should be able to log in with valid credentials.
2. **REQ-002**: User should not be able to log in with invalid email.
3. **REQ-003**: System should display an error message for invalid inputs.

***Steps to Create RTM**:*

1. Assign IDs: REQ-001, REQ-002, REQ-003.
2. Create test cases:
   - TC-001: Verify login with valid email and password.
   - TC-002: Verify login with invalid password.
   - TC-003: Verify login with non-existent email.
   - TC-004: Verify error message for invalid email.
3. Map requirements to test cases:
   - REQ-001 → TC-001, TC-002
   - REQ-002 → TC-003
   - REQ-003 → TC-004
4. Populate the RTM with status, defect IDs, and comments as testing progresses.

***Tools for Creating RTM***

You can create an RTM using:

- **Excel/Google Sheets**: Simple and widely used.
- **Test Management Tools**: Tools like Jira, TestRail, or Zephyr provide built-in RTM features.
- **Custom Templates**: Create your own RTM template based on project needs.

***Best Practices for RTM***

1. **Start Early**: Begin creating the RTM during the requirement analysis phase.
2. **Keep It Updated**: Regularly update the RTM as requirements or test cases change.
3. **Ensure Traceability**: Ensure every requirement is linked to at least one test case.
4. **Collaborate**: Work with stakeholders to validate requirements and test cases.
5. **Use Automation**: For large projects, use tools to automate RTM creation and maintenance.

***Benefits of RTM***

1. **Complete Test Coverage**: Ensures no requirement is left untested.
2. **Transparency**: Provides a clear view of the testing progress and status.
3. **Change Management**: Helps assess the impact of requirement changes on testing.
4. **Quality Assurance**: Improves the overall quality of the software by ensuring all requirements are validated.

***When to Use RTM***

- During **Requirement Analysis** to map requirements to test cases.
- During **Test Execution** to track the status of test cases and defects.
- During **Test Closure** to verify that all requirements are tested and met.

*In summary, the **Requirement Traceability Matrix (RTM)** is a vital tool for ensuring that all requirements are tested and tracked throughout the software development lifecycle. It helps maintain alignment between requirements, test cases, and defects, ensuring a high-quality product.*