Executive Summary

This document specifies the functional (e.g., activities performed and outputs produced) as well as nonfunctional (e.g., performance and security) features of the system to be developed or acquired. The requirements document is a key resource for systems development, user involvement and project management.  

The requirements document is created early in the system life cycle and is subject to formal/informal reviews by the clients, systems developers, project managers and testers throughout the life cycle. It forms the basis for ongoing development and testing of the system to meet the requirements of the client. It thus supplies sufficient information to the client to establish a solid foundation for subsequent assessment and approval.  It also provides the development/acquisition team with a basis for on-going management and testing.

Contents

Definitions and Terms

1. Overview and Business Drivers
   • Business Needs (edit and modify to fit your needs)
2. Background Information
3. Application Functional Requirements
4. Information Models (Use Cases, Class Diagrams, Sequence Diagrams)
5. Logical Architecture (Application Pattern)
6. Architecture and Integration Requirements (General)
   • Distributed Architecture Requirements
   • Interface/Integration Requirements
7. Architecture and Integration Requirements (Specialized based on the Interview)
8. Operational Requirements (Generic)
   • Security/Permission Requirements
   • Performance Requirements
   • Hardware Requirements
   • Software Requirements
9. Vendor  Support Requirements
   • Application Service Provider (ASP) Support
   • Back Up and Maintenance Support
   • Documentation Support
   • Training Support
10. SOA Considerations
    • Suggestions