SYSTEM SPECIFICATION
1.0 Introduction
This section provides an overview of the entire system or product. This document describes all subsystems including hardware, software, human activities, documents, and process.
Overall business s goals and project objectives are described.
1.2 System statement of scope
A description of the entire system is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail.
1.3 System context
The system is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the "big picture."
1.4 Major constraints
Any business or product line constraints that will impact the manner in which the system is to be specified, designed, implemented or tested are noted here.
2.0 Functional and Data Description
This section describes overall system function and the information domain in which it operates.
A context-level model of the system architecture is presented.
A context-level model of the system architecture is presented.
2.1.2 Subsystem overview
Each subsystem noted in the architecture model is described briefly.
Top-level data objects that will be managed/manipulated by the system or product are described in this section.
Data objects and their major attributes are described.
2.2.2 Relationships
Relationships among data objects are described using an ERD- like form. No attempt is made to provide detail at this stage.
2.2.3 System level data model
An ERD for the system is developed (this section may be omitted).
The system's interface(s) to the outside world are described.
Interfaces to other machines (computers or devices) are described.
2.3.2 External system interfaces
Interfaces to other systems, products or networks are described.
2.3.3 Human interface
An overview of any human interfaces to be designed for the system/product is presented.
3.0 Subsystem Description
A description of each subsystem is presented.
A detailed description of each subsystem is presented. Section 3.1 is repeated for each of n subsystems.
A statement of scope for subsystem n is presented.
3.1.2 Subsystem flow diagram
A diagram showing the flow of information through the subsystem and the transformation that it undergoes is presented.
3.1.3 Subsystem n components
A detailed description for each component of subsystem n is presented. Section 3.1.3 is repeated for each of k components.
3.1.3.2 Component k interface description
Special performance required for the subsystem is specified.
3.1.5 Design Constraints
Any design constraints that will impact the subsystem are noted.
3.1.6 Allocation for Subsystem n
The allocation for implementation (e.g., will the subsystem be implemented in hardware, software, by a human, etc.) is described.
A diagrammatic model for each subsystem is presented. Section 3.2 is repeated for each of n subsystems.
4.0 System Modeling and Simulation Results
If system modeling and simulation and/or prototyping is conducted, these are specified here.
The system modeling approach (including tools and/or mathematical models) is described.
4.2 Simulation results
The results of any system simulation are presented with specific emphasis on data throughput, timing, performance, and/or system behavior.
4.3 Special performance issues
Special performance issues are identified.
4.4 Prototyping requirements
If a system prototyping is to be built, its specification and implementation environment are described here.
5.0 Project Issues
An overview of the overall system/product project plan is presented.
The results of system-level cost estimates are presented.
5.2 Project schedule
A top-level schedule for the development project is proposed.
6.0 Appendices
Presents information that supplements the System Specification.
If the specification is developed for a business system, a description of relevant business processes is presented here.
6.2 Product Strategies
If the specification is developed for a product, a description of relevant product strategy is presented here.
6.3 Supplementary information (as required)