The document provides instructions for completing a requirements traceability matrix, including fields to populate for each requirement such as a unique ID, associated IDs, the requirement description, status, linked architectural/design documents, test cases, and more. It includes an example requirements traceability matrix template.
The document provides instructions for completing a requirements traceability matrix, including fields to populate for each requirement such as a unique ID, associated IDs, the requirement description, status, linked architectural/design documents, test cases, and more. It includes an example requirements traceability matrix template.
The document provides instructions for completing a requirements traceability matrix, including fields to populate for each requirement such as a unique ID, associated IDs, the requirement description, status, linked architectural/design documents, test cases, and more. It includes an example requirements traceability matrix template.
The document provides instructions for completing a requirements traceability matrix, including fields to populate for each requirement such as a unique ID, associated IDs, the requirement description, status, linked architectural/design documents, test cases, and more. It includes an example requirements traceability matrix template.
Download as XLSX, PDF, TXT or read online from Scribd
Download as xlsx, pdf, or txt
You are on page 1of 4
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, C/I/O, 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. Associated ID(s): This column should contain the ID of any associated utilities used for requirements tracking such as a repository, pipeline document, etc. 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. Functional Requirement: This column should be populated with a description of the functional requirement. Status: This column should be populated with the current status of the functional requirement. Architectural/Design Document: This column should be populated with a description of the architectural/design document linked to the functional requirement. Technical Specification: This column should be populated with a description of the technical specification linked to the functional requirement. System Component(s): This column should be populated with a description of the system component(s) linked to the functional requirement. Software Module(s): This column should be populated with a description of the software module(s) linked to the functional requirement. Test Case Number: This column should be populated with the test case number linked to the functional requirement. Tested In: This column should be populated with the module that the functional requirement has been tested in. Implemented In: This column should be populated with the module that the functional requirement has been implemented in.
Verification: This column should be populated with a description
of the verification document linked to the functional requirement.
Additional Comments: This column should be populated with
any additional comments REQUIREMENTS TRACEABILITY MATRIX Project Name: Celestial Authentication AT-T101-1.0 Project Manager Na Jitendra Bansiwal Project Description: Provide the secure centralize authentication Assoc Technical Assumption(s) Functional Architectural/Design Technical System ID Status ID and/or Customer Need(s) Requirement Document Specification Component(s) 001 BR-1 User login User login with username and password Testing 002 BR-2 User Registration New user can register Completed 003 BR-3 Change Password Change password Completed 004 BR-4 Update profile Update profile In Progress 005 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
UP Template Version: 11/30/06 Page 2 of 4
REQUIREMENTS TRACEABILITY MATRIX
Software Test Case
Tested In Implemented In Verification Module(s) Number User management T-1 User management T-2 User management T-3 User management T-4