CSCI 6620 Software Engineering                  Dr. Levine
CONTRACT SPECIFICATION                       

Consider your contract as a requirements description (where
clearly each stage of the development process can be considered a
subcontract).  The contract stipulates criteria by which the
successful completion of your project will be judged.

The contract must include:

I. A Cover Sheet, as on all assignments;
               Contract for <your software system>
               Document Description:
               Group Members:
               Authors of documents and sections they authored   
               Course Name, Professor's Name, Date

II. Statement of System (about a page)
    what it does, its important features

III. Rationale of System 
    who will use it, how will it help them

IV. Functional Behavior (especially the user interface)
     a) the menu
     b) other interfaces
     c) input by type and format and results of each input  
     d) output on each media
     e) any input not handled
     f) error handling

V. Nonfunctional Behavior
     a) physical environment
     b) constraints (timing, storage, etc.)
     c) performance goals, such as response time

VI. Data Definition
    description of all data entities that are known to the client

VII. Description of critical decisions and tradeoffs of design 

VIII. Reusability considerations
     design with/ for reuse
     consumer   / producer

IX. Description of documentation to be supplied and timelines
     a) user manual
     b) test plan
     c) on-line help

X. Glossary

XI. Index