Requirements Traceability Matrix

PLAN IT!

Requirements Traceability Matrix

• There are various types of Requirements:– Functional Requirements– Technical Requirements– Security Requirements– Vendor Requirements

• The Requirement Type is recorded in Column 1

• Requirements are usually grouped by Type

Requirements Traceability Matrix

• Each requirement contains the following:– A unique requirement number– A brief, high level description of the requirement – The requirement priority (Must Have, Should Have,

or Nice to Have)– The requirement source (the requestor)– The objective (from the Project Charter) to which

the requirement relates– Where the requirement is located in the Work

Breakdown Structure

Requirements Traceability Matrix

• The second half of the RTM is completed as the project progresses:– Design Document Reference– Code Module/Reference– Verification– Verifier– Use Case Reference– Test Case Reference– User Acceptance Validation– Comments

Requirements Traceability Matrix

• Used correctly, the RTM is a running history of the project requirements, including Change Requests, from identification through implementation, to ensure that every requirement has been allocated appropriately through design, build (development), testing, and final sign-off and acceptance.