Project Name
Traceability Matrix
TEMPLATE
Change Control Page
The following information is being used to control and track modifications made to this
document.
1)
Revision Date:
Author:
Section(s):
Page Number(s):
Summary of Change(s):
Title Page
Document Name:
Project Name
Requirements Traceability Matrix
Creation Date:
Month Year
Document Number:
XX-XXXX-XXXXXXXXX
Project Number:
Task: XXXXXXXXXXXXXX
Created by:
XXXX XXXXXX
Approver:
__________________________
Name and Organization
Concurrence:
_________________________
Name and Organization
Table of Contents
Preface..............................................................................................................................................ii
1.
Overview...............................................................................................................................1-1
1.1 Scope..........................................................................................................................1-1
1.2 Responsibilities............................................................................................................1-1
2.
Requirements Traceability Matrix.........................................................................................2-1
2.1 Description of Matrix Fields.......................................................................................2-1
2.2 Requirements Traceability Matrix...............................................................................2-1
Project Name Req. Traceability Matrix i
11/98
Preface
Document Version Control: It is the reader's responsibility to ensure they have the latest version
of this document. Questions should be directed to the owner of this document, or the project
manager.
This document was generated by the Project Name project team. System/Project Name will be
developed for the Organizational Name.
Lifecycle Stage: Project Name is in the Requirements stage of the software lifecycle.
Approval: A completed stage exit will constitute approval of this document.
Document Owner: The primary contact for questions regarding this document is:
Author=s Name, Author=s Function, e.g., Project Planner
Project Name Team
Phone: (XXX) XXX-XXXX
Primary email: XXXX
cc mail:XXXX
Privacy Information
This document may contain information of a sensitive nature. This information should not be
given to persons other than those who are involved in the Project Name project or who will
become involved during the lifecycle.
Project Name Req. Traceability Matrixii
11/98
1. Overview
1.1 Scope
The requirements traceability matrix is a table used to trace project life cycle activities and work
products to the project requirements. The matrix establishes a thread that traces requirements
from identification through implementation. Document the scope of the requirements traceability
matrix in this section.
1.2 Responsibilities
The requirements traceability matrix will be maintained by the project manager or designee;
however, input to the table may be required from other team members. Document the
responsibilities in this section.
Project Name Req. Traceability Matrix
11/98
1-1
2. Requirements Traceability Matrix
2.1 Description of Matrix Fields
Develop a matrix to trace the requirements back to the project objectives identified in the Project
Plan and forward through the remainder of the project life cycle stages. Place a copy of the
matrix in the Project File. Expand the matrix in each stage to show traceability of work products
to the requirements and vice versa. The requirements traceability matrix should contain the
following fields:
$
A unique identification number containing the general category of the requirement (e.g.,
SYSADM) and a number assigned in ascending order (e.g., 1.0; 1.1; 1.2).
The requirement statement.
Requirement source (Conference; Configuration Control Board; Task Assignment, etc.).
Software Requirements Specification/Functional Requirements Document paragraph number
containing the requirement.
Design Specification paragraph number containing the requirement.
Program Module containing the requirement.
Test Specification containing the requirement test.
Test Case number(s) where requirement is to be tested (optional).
Verification of successful testing of requirements.
Modification field. If requirement was changed, eliminated, or replaced, indicate disposition
and authority for modification.
Remarks.
2.2 Requirements Traceability Matrix
Project Name Req. Traceability Matrix
11/98
2-1
Project Name
Requirements Traceability Matrix
Unique
Number
Requirement
Source of
Requirement
Software Reqs. Spec/
Functional Req. Doc.
Design
Spec.
Program
Module
Test
Spec.
Test
Case(s)
Successful
Test
Verification
Modification
of
Requirement
Remarks
Objective 1:
Project Name Req. Traceability Matrix
2-2
11/98
