Do you have questions ? We got the answers!

Ask a question:

0
How do you build a requirement traceability matrix?

Solved 1 Answers 32 Views
How do you build a requirement traceability matrix?

1 Answer

1
Best answer

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:

  1. Create a spreadsheet (excel sheet) with below columns:
    • Requirement ID
    • Requirement description
    • Test Scenario ID
    • Test Case ID
    • Status
    • Defects
  2. Analyze and capture the detailed requirements:
    • Use Cases
    • Business logics
    • Functional logics
    • Validation/Error Messages
    • Product requirement specifications
    • Functional requirement specifications
  3. Analysze and prepare the test scenarios to be covered.
  4. 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
answered Aug 10 by rajeevtechexpert (224 points)
edited Aug 17 by rajeevtechexpert

Top Contributors

  • 4970 pointsstbadmin

    34 questions 454 answers218 comments

  • 430 pointsSunilBhaskar

    40 questions 14 answers26 comments

  • 425 pointsMehedi

    36 questions 3 answers14 comments

  • 354 pointsSoft Tester

    43 questions 0 answers4 comments

  • 342 pointssumitkumarwatts

    0 questions 12 answers0 comments

  • 327 pointsKeeshaGolden

    0 questions 17 answers2 comments

  • 322 pointsVipul Sharma

    44 questions 0 answers24 comments

  • 310 pointsvysh.sharma

    25 questions 0 answers0 comments

  • 267 pointsOnkar_Nimje

    33 questions 15 answers15 comments

  • 258 pointsVanitha

    26 questions 0 answers6 comments

...