As the term progresses, I will learn what distinguishes a final from a first draft, and this page will be split into two that share much of their contents.

You are to produce a draft or final copy of a complete requirements specification of the identified scope of the system that your group is prototyping in SE 490: This complete requirements specification can be in any of a number of forms, including, but not limited to:

• a complete Software Requirements Specification (SRS),
• a complete user's manual (UM),
• a complete set of complete UML descriptions (at least a domain model, an object model, a use case model, and a complete, covering set of use cases),
• a complete online help system,
• a complete set of complete user stories and for each user story, and associated complete, covering set of test cases, or
• a set of artifacts accepted by the course prof as providing sufficient completeness.

The key criterion for completeness is that the group, in writing the specification, is forced to flesh out all the requirements that are already present in the chosen scope of the system that you are prototyping in SE 490. To start producing this specification from the three artifacts that you handed in as Deliverables 1, 2, and 3, you will have to produce an updated version of each of these three artifacts in which:

• all defects noticed by anyone, including your TA, have been fixed, and
• all the artifacts are consistent with each other.

The main additional information, beyond that coming from the three artifacts, is

• a complete set of scenarios for each use case, including the typical and all exception and alternative scenarios, and
• a complete user interface that is used in these scenarios.

All other notation-specific variations in the specification fall out of this information.

To try to be more precise, your specification will include at least

• cover page + table of contents + page numbers,
• a glossary of terms,
• a revised domain model with superimposed world diagram,
• a revised use case diagram,
• a typical scenario for each use case, expressed in natural langauge in one of several possible formats:
  • the format of Lihua Ou's WD-Pic User's Manual,
  • multicolumn format as in the Scenarios and Use Cases slides,
  • single column, multicolor format, with the steps of each actor or process being in a different color,
  • the format of Adobe Acrobat's online help pages,
• all needed exceptional scenarios for each use case, especially to deal with assumptions that do not hold,
• all needed alternative scenarios for each use case, and
• a user-interface description that is associated with these scenarios.

You MUST follow any relevant advice given in the ``User's Manual Advice'' slides.