Table of Contents

Project Title

  1. Overview
    1. Objective
    2. References
    3. Outstanding Issues
  2. Current Environment
    1. Organization Profile
    2. Business Function
    3. Component or System Description
    4. Deficiencies
  3. Requirements
    1. Goals
    2. Input and Output Requirements
    3. Data Requirements
    4. Functional Requirements
    5. Performance Requirements
    6. System and Communication Requirements
    7. System Security Requirements
    8. Backup and Recovery Requirements
    9. Support Considerations
    10. Hardware Requirements
    11. Software Requirements
    12. Usability Requirements
    13. Training Requirements
    14. Transition Requirements
    15. Testing Requirements
  4. Project Points of Contact
  5. Glossary
  6. Approvals/Concurrence



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.

Project Title

Reference the SC strategic plan/operations project plan name or proposed new project title.

  1. Overview

Reference the SC strategic plan/operations plan project description or proposed new project description and business model requirement being satisfied.

1.1 Objective

    1. References

    2. Provide all references to SC and DOE documents used in developing these requirements.

    3. Outstanding Issues

      Identify any outstanding, unresolved issues, which are part of the requirements process.

2.0 Current Environment

    1. Organization Profile

    2. Provide a description of the SC organization/business environment currently serviced by existing systems and/or technology solutions.

    3. Business Function

    4. Identify the specific business functions to be addressed by the requirement document.

    5. Component or System Description

    6. Identify specific Information Resource Catalog and/or Technology areas in the current environment to be impacted.

    7. Deficiencies

Identify any major system deficiencies to be addressed in the requirement document.

3.0 Requirements

    1. Goals

    2. Identify the high level goals linked to the SC business model that contribute to the organization.

    3. Input and Output Requirements

    4. Identify all high level business input and output requirements and include references to JAD/RAD use cases as appropriate.

    5. Data Requirements
    6. Identify all high level data input and output requirements and include references to JAD/RAD use cases as appropriate.

    7. Functional Requirements
    8. Document all system functional requirements to be satisfied by the project.

    9. Performance Requirements
    10. Document necessary, specific system performance requirements for a successful deployment of an operational configuration.

    11. System and Communication Requirements
    12. Document all system and communication requirements including networking, intranet, extranet, remote access, corporate system interfaces and internet connectivity requirements.

    13. System Security Requirements
    14. Document all system security requirements referencing SC/DOE cyber security planning criteria.

    15. Backup and Recovery Requirements
    16. Document all system backup and recovery requirements.

    17. Support Considerations
    18. Document all system SC support requirements.

    19. Hardware Requirements
    20. Document all system hardware requirements for development, test and production configurations

    21. Software Requirements
    22. Document all system software requirements for development, test and production configurations.

    23. Usability Requirements
    24. Document all system usability requirements for SC user base.

    25. Training Requirements
    26. Document all system training requirements.

    27. Transition Requirements
    28. Document all system transition to production status requirements.

    29. Testing Requirements

Document all system testing requirements referencing use case information as appropriate.

  1. Project Points Of Contacts
  2. 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.

  3. Glossary
  4. Provide a glossary of all technical terminology and acronyms used within the document.

  5. Approvals/Concurrence

Include an appropriate SC concurrence/approval section