Spreadsheet: 1170b235-3dfc-442d-aa57-9179d9c3c69f
Sheet: Instructions

 | For detail regarding the practice of Requirements Management, please refer to the Requirements Management Section of  the Process 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.
 | 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.
 | Scope of the Product
 | Data Requirements
 | Look and Feel Requirements
 | Usability Requirements
 | Performance Requirements
 | Operational Requirements
 | Maintainability and Portability Requirements
 | Security Requirements
 | Cultural and Political Requirements
 | Legal Requirements
 | Priority:  This column should be populated with a high, medium and low weighting.
 | 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.
 | Design Constraints:  This column should be populated with limitations and restrictions on the design of the product.
 | 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.
 | Validation:  This column should be populated with a description of the validation document linked to the functional requirement.
 | Verification: This column should be populated with a description of the verification document linked to the functional requirement.
 | Relates to Objectives In Charter: This column should be populated with information relating the requirement to the Charter.
 | Manifests in WBS Deliverable: This column relates to the deliverable in the WBS that meets the requirement - can use WBS ID coding if needed.
 | Risks Associated: This column should reflect whether or not the requirement has been assessed for risk. Please answer yes or no.
 | Change: This column should be populated with a description of the change document linked to the functional requirement.
 | Implementation Date: This column should be populated with a date of when the change was implemented. If no change then please list N/A.
 | Additional Comments: This column should be populated with any additional comments