This document shall be called the Software Requirements Specification. Its structure may conform to any number of different outlines. I suggest that you follow the sample outline of ANSI/IEEE Standard 830-1984, a hard copy of which you received during our discussion of textbook chapter 4. I will also provide you with example documents from previous semesters.

The specification methods described in chapters 4, 6 and 7 should be employed in the construction of this document. Use the methods that are most appropriate to your system structure. I have a couple shareware tools that can be used to build graphical models (data flow diagrams, object models, entity-relation models); you may also have tools of your own, or wish to search for such tools on the web.

Designate one members of the team to be the requirements document editor. The editor is responsible for assembling the document from other documents supplied by teammates, assuring a uniform format and pagination, and building the Table of Contents. Include a Credits section to tell me who contributed what to the document and to the prototype.

Some of the document subsections will be more detailed than others. If the level of detail requires more than one paragraph, break down the numbering to a third level (or fourth, etc, if necessary). For instance, Section 3.1 will need to be organized into 3.1.1, 3.1.2, 3.1.3, etc.

An interactive software prototype will be developed using appropriate development tools.

I will return the initial requirements document to you as soon as I can, so you can revise it, in response to my comments and suggestions. You will demonstrate the initial prototype to me and/or your project sponsor as soon as possible on or after the due date. You will revise the prototype in response to comments and suggestions given during the demonstration.