This document provides an outline for the Software Requirements Specification. It is modeled after the IEEE 830-1003 standard (page 117 of your text), and adapted from Software Engineering: An Object Oriented Perspective, by Eric Braude. Use this outline to structure the requirements specification for your software.
Indicate the purpose of this document, that is the Software Requirements Specification. Purpose does not refer to the purpose of the application.
What aspects of the application does this document cover ?
Make this general enough so that it is unlikely to change much in future versions.
Compare the product to other related or competing products.
Convey the overall concept of the application by appropriate means. You can use words, state-transition diagrams or some other means.
Preliminary sketches of key user interfaces. You will be providing a detailed view of the user interfaces in Section 3.
Example: Uses a joystick to ....
Example: Interfaces with SABRE reservation system...
Example: Interfaces with the Internet via a modem....
Requirements for executing on a particular installation, for example versions in various languages.
Summary of the major functions of the application. More detailed than Secton 1.5; less detailed than Section 3. This is the ``user'' view of the functions.
Indicate what kind of people the product is designed for, that is a profile of the typical user.
Indicate conditions that may limit the developer's options. Example: hardware constraints, software constraints.
This is the ``system requirements'' specification. This provides a detailed view of the functional, non-functional, and interface requirements.
Minimum required speed, response time, and/or time to complete, memory requirements etc.
Example: Shall utilize an object-oriented design, use Java, run under Windows 2000.
See discussion of Appendices on page 118 of your text.