STEP 3. REQUIREMENTS
Table of Contents
REQUIREMENTS DOCUMENT INSTRUCTIONS
The Requirements document is a joint document with three (3) deliverables
The Requirements documents should include 6 sections: Overview, Current Environment, Requirements, Points of Contact, Approvals/Concurrence and a Glossary. A sample table of contents crosswalk is attached showing where areas of the SC Information Management (IM) team require formal input1.
Reference the SC strategic plan/operations project plan name or proposed new project title.
Reference the SC strategic plan/operations plan project description or proposed new project description and business model requirement being satisfied.
Provide all references to SC and DOE documents used in developing these requirements.
2.0 Current Environment
Identify the specific business functions to be addressed by the requirement document.
Identify specific Information Resource Catalog and/or Technology areas in the current environment to be impacted.
Identify any major system deficiencies to be addressed in the requirement document.
Identify the high level goals linked to the SC business model that contribute to the organization.
Identify all high level business input and output requirements and include references to JAD/RAD use cases as appropriate.
Identify all high level data input and output requirements and include references to JAD/RAD use cases as appropriate.
Document all system functional requirements to be satisfied by the project.
Document necessary, specific system performance requirements for a successful deployment of an operational configuration.
Document all system and communication requirements including networking, intranet, extranet, remote access, corporate system interfaces and internet connectivity requirements.
Document all system security requirements referencing SC/DOE cyber security planning criteria.
Document all system backup and recovery requirements.
Document all system SC support requirements.
Document all system hardware requirements for development, test and production configurations
Document all system software requirements for development, test and production configurations.
Document all system usability requirements for SC user base.
Document all system training requirements.
Document all system transition to production status requirements.
Document all system testing requirements referencing use case information as appropriate.
Identify all project contacts including champions, team leads, project leads, team members, users, non-SC system contacts and any other key POCís as required.
Provide a glossary of all technical terminology and acronyms used within the document.
Include an appropriate SC concurrence/approval section