For detail regarding the practice of Requirements Management, please refer to the Requirements

Management Practices Guide

Instructions For Completing This Document

1.) Complete the Project Name, Project Manager Name, and Project Description fields
2.) For each issue identified, complete the following:
ID: A unique ID number used to identify the traceability item in the requirements
traceability matrix.
Requirement ID: This column should contain the unique idenfier of the requirement.
It could be a system generated number if using a utility, or manually assigned in a
requirements document by the requirements author/analyst.
Associated Requriement ID(s): This column should be populated with the
associated requirements that will be affected if this requirement is changed.
Technical Assumption(s) or Customer Need(s): This column should be populated
with a description of the technical assumption or customer need linked to the
functional requirement.
Requirement Description: This column should be populated with a brief description
of the requirement.
Status: This column should be populated with the current status of the requirement.

Optional Requirement Type: This column should be populated with the type of requirement:
functional, non-functional, etc.
Optional Priority: This column should be populated with the importance of the requirement as
designated by/or agreed upon by the users.
(H High, M Medium, L Low).
Optional Complexity: This column rates the difficulty of implementing the requirement as
designated by the assigned individual.
(H High, M Medium, L Low).
Optional Assigned To: Identifies an individual or group responsible for fulfilling this
requirement.
Architectural/Design Document: This column should be populated with a
description of the architectural/design document (or reference) linked to the
functional requirement.(a.k.a. "Trace To Design")
Technical Specification: This column should be populated with a description of the
technical specification linked to the requirement.
System Component(s): This column should be populated with a description of the
system component(s) linked to the requirement.
Software Module(s): This column should be populated with a description of the
software module(s) linked to the requirement.
If necessary, repeat the following block and labeled with each type of tests:
Integration Test , System Test, User Acceptance Test, etc.
Test Case Number: This column should be populated with the test case number
linked to the requirement. (a.k.a. "Trace to Test Case")
Optional Tested In: This column should be populated with the module that the requirement
has been tested in.
Optional Implemented In: This column should be populated with the module that the
requirement has been implemented in.
Optional Verification: This column should be populated with a description of the verification
document linked to the requirement.
Optional Additional Comments: This column should be populated with any additional
comments
Note: Dropdown lists (allowable values tables) are defined in "AVT" worksheet. Customize as needed
REQUIREMENTS TRACEABILITY MATRIX
Project Name: <optional> Project Name: <optional>
Project Manager Name: <required> Project Manager Name: <required>
Project Description: <required> Project Description: <required>
(optional) (optional) (optional) (optional) (optional)
Req Assoc Technical Assumption(s) Description Architectural/Design Technical System
ID Status Type Priority Complexity Assigned To
ID Req ID and/or Customer Need(s) Document Specification Component(s)
001 1.1.1
002 2.2.2
003 3.3.3
004 4.4.4
005 5.5.5
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034

EPLC Template Version: xx/xx/xx Page 3 of 5

REQUIREMENTS TRACEABILITY
REQUIREMENTSMATRIX
TRACEABILITY MATRIX
Project Name:
Project Manager Name:
Project Description:
(optional) (optional) (optional) (optional) (optional)
Req Assoc Software Test Case Additional
ID Tested In Implemented In Verification
ID Req ID Module(s) Number Comments
001 1.1.1
002 2.2.2
003 3.3.3
004 4.4.4
005 5.5.5
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034

EPLC Template Version: xx/xx/xx Page 4 of 5

 Status Type Priority Complexity
InProgress Functional L L
Testing NonFunctioM M
Completed Security H H