This template was purchased by AuditNet from a third party under a work for hire

agreement. However, while we have attempted to provide accurate information no

representation is made or warranty given as to the completeness or accuracy of the
template. In particular, you should be aware that the template may be incomplete,
may contain errors, or may have become out of date. While every reasonable
precaution has been taken in the preparation of this template, neither the author
nor AuditNet assumes responsibility for errors or omissions, or for damages
resulting from the use of the information contained herein. The information
contained in this document is believed to be accurate. However, no guarantee is
provided. Use this information at your own risk.
 Instructions For Completing This
1.)
2.)
 For detail regarding the practice of Requirements Management, please refer to th
1.1 Purpose
The purpose of the Requirements Management Plan is to describe all the processes, roles and responsibilities associated wi
Requirements define the scope of a project and the criteria for its success. Requirements describe what the system must do
project. Managing requirements effectively increases the probability of a project’s success. Therefore, defining clear, correct
development project and for maintaining the integrity and performance of a system over time.
1.2 Scope
The Requirements Management Plan identifies the process and procedures used to plan, develop, monitor and control requir
requirement management policies and procedures.
Comprehensive and well-defined requirements are critical to a project’s success at every step.

Instructions For Completing This Doc

Complete the Project Name, C/I/O, Project Manager Name, and Project Description fields
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 reposit
Technical Assumption(s) or Customer Need(s): This column should be populated with a description of the technical assump
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 link
Technical Specification: This column should be populated with a description of the technical specification linked to the function
System Component(s): This column should be populated with a description of the system component(s) linked to the functiona
Software Module(s): This column should be populated with a description of the software module(s) linked to the functional requ
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 requiremen
Additional Comments: This column should be populated with any additional comments
REQUIREMENTS TRACEABILITY MATRIX
Project Name: <optional>

Project Manager N<required>

Project Description<required>

Assoc Technical Assumption(s) Functional Architectural/Design Technical

ID Status
ID and/or Customer Need(s) Requirement Document Specification

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
UP Template Version: 11/30/06 Page 4 of 13
REQUIREMENTS TRACEABILITY MATRIX
Project Name: <optional>

Project Manager N<required>

Project Description<required>

Assoc Technical Assumption(s) Functional Architectural/Design Technical

ID Status
ID and/or Customer Need(s) Requirement Document Specification

030
031
032
033
034

UP Template Version: 11/30/06 Page 5 of 13

 REQUIREMENTS TRACEABILITY MATRIX
Project Name: <optional>

Project Manager Name: <required>

Project Description: <required>
Test
System Software Tested
Case Implemented In Verification
Component(s) Module(s) In
Number

UP Template Version: 11/30/06 Page 6 of 13

 REQUIREMENTS TRACEABILITY MATRIX
Project Name: <optional>

Project Manager Name: <required>

Project Description: <required>
Test
System Software Tested
Case Implemented In Verification
Component(s) Module(s) In
Number

UP Template Version: 11/30/06 Page 7 of 13

 Additional
Comments

UP Template Version: 11/30/06 Page 8 of 13

 Additional
Comments

UP Template Version: 11/30/06 Page 9 of 13

General Requirement Document
·         Is a functional overview of the system provided?
·         Have the software and hardware environments been specified?
·         Are implementation assumptions stated?
·         Have the functionality of hardware or software interacting with the system been properly specified?
·         Has every acronym been defined?
·         Are boundaries, scope, and context of the requirements identified?
·         Is the document easily searchable for modification, and addition of requirements?
·         Do the requirements avoid specifying design?
·         Are the requirements at a fairly consistent level of detail?
·          Are the requirements clear enough to be turned over to an independent group for implementation and still b
·         Does the set of requirements adequately address all appropriate exception conditions?
·         Can the requirements be implemented within known constraints?
·         Are all cross-references to other requirements correct?
·         Are all missing items or unresolved issues identified with an owner, and a time-line for closing it?
Business and Functional Requirements
·         Are the high-level business objectives described?
·         Are the requirements understandable by all stakeholders?
·         Is the value to the business identified? (Cost savings, reduced inventory, etc.)
·         Is the value to the customer identified? (New features, improved usability, etc.)
·         Does this requirement answer the question ‘Why is this needed’?
·         Does the set of functional requirements meet the needs outlined by business requirements? (e.g. complete,
·         Is the relation between functional and the non-functional requirements clear?
Interface Requirements
·         Are all inputs to the system specified, including their source, accuracy, range of values, parameters and freq
·         Are all outputs from the system specified, including their destination, accuracy, range of values, parameters
·         Are all screen formats specified?
 ·         Are all report formats specified?
·         Are all interface requirements between hardware, software, personnel, and procedures included?
·         Are all communication interfaces specified, including handshaking, error-checking, and communication prot
Technical Requirements
·         Are all inputs to a function sufficient to perform the required function?
·         Are undesired events/inputs considered and their required responses specified?
·         Have the types, initial values, units been defined for every object attribute?
·         Have the parameter and return types of all object operations been defined?
·         Have the accuracy, precision, range, type, rate, units, frequency of inputs and outputs been specified for eac
·         Is the expected response time, from the user's point of view, specified for all operations?
·         Is the level of security specified?
·         Is the reliability specified, including the consequences of software failure, the vital information that needs to
·         Is the maximum memory specified?
·         Is the maximum storage specified?
Individual Requirements
·         Is the requirement clear and concise?
·         Is the requirement stated in as simple a form as possible?
·         Is the requirement testable/verifiable?
·         Is the requirement correct?
·         Is the requirement in scope? (i.e., the system will be considered incomplete if even one requirement is left o
·         Is the requirement as modifiable as possible?
·         Is the requirement written in the customer’s language, using the customer’s terminology?
·         Is the requirement necessary?
·         Does this requirement answer the question ‘How Well’?
·         Is each requirement implementation independent?
System Requirements:
·         Reliability
o        Are the reliability requirements specified?
o        Are the availability (up time) requirements specified?
o        Are the serviceability requirements specified?
 o        Are the robustness requirements specified?
·         Performance
o        Are the response time or latency requirements specified?
o        Are the throughput requirements specified?
o        Are the data volume requirements specified? (input, stored, output)
o        Are the peak or short-term load requirements specified?
·         Safety/Security
o        Are the security requirements specified?
o        Are the safety requirements specified?
·         Configuration
o        Are the supported configurations specified?
o        Are the compatibility requirements specified? (backwards, other applications, etc.)
·         Usability
o        Are the usability requirements specified?
o        Are the internationalization/localization requirements specified?
o        Are the look and feel requirements specified? (e.g. color schemes, standards, etc.)
·         Operational
o        Are all operational constraints or requirements specified? (e.g. network limitations, memory limita
Yes No Status