Requirement specification Document
Suggested Outlines
Sources: Prof. Lewis, SUNY Stony Brook
Other source of information: Click here
Title
Title, Author, Date, Version Number
Related Documents
For example, the Requirements Document, an Object Library, a Standards
Document.
Objectives
An overview of the system, so that the reader can understand the rest of
the document. What is the system supposed to do. What are its key features.
What are its non-functional requirements.
Object Decomposition
Specification of objects to be used in system. For each object, its methods and visible methods. Relations between objects. Inheritance, etc.
Class Diagrams and Object Diagrams
Functional Decomposition
Specification of functional components. For each component, its inputs
and outputs, and the functions it performs
Use Cases
Specific use cases describing how the various actors use the system.
Dynamic Models
Event Traces, State Machines, Sequence Diagrams, Activity Diagrams, Swimlane
Diagrams
User Interface
The entire user interface. Pictures of every form with every control.
Specification List
Numbered list of detailed specifications. What happens when each control
is used. Every detail of the system operation must be covered
Error Conditions
Numbered list of all error situations not covered above and what the system
is supposed to do in each case.
Non-functional Requirements
System Requirements
Schedule and Budget