Client Contract I (w/ Schedule I)

Due: February 6, 2001

Your team's second deliverable document

General

• Official statement of what is required, to confirm agreement between client and team
• Formal: Acrobat/PDF (preferred), Word, etc.
  • Acrobat on PC w/ scanner in glab
  • Unix ps/pdf tools
• Due on February 6
  • Hand deliver hard copy w/ signatures
    • to Boss at start of class
    • to Client same day
  • Email to notify that the electronic version is in your Library
    • the Boss
    • your Client
• Use hierarchical section numbering
  • In paragraphs describing requirements
  • Use matching numbering in diagrams! (Same as paragraphs)
  • See the Outline Details below for an example
• Page length guidelines
  • In the outline below I have included page budget suggestions in curly brackets "{}" with a few headings. These are only suggestions, and if you look at the items I think you will see that they map to the number of diagrams, etc. Use your discretion.
  • I don't expect--nor want to see--more than (say) one paragraph per section or sub-section, with no more than three levels of subs-sections (sub-functionality sections).

Outline

• Top Level
  • Title Page {1 page}
  • Preface {~1/2 page or less}
  • Introduction {~1/2 page or less}
  • User Requirements Specification {~1-2 pages including diagrams}
  • System Requirements Specification {~2-4 pages including diagrams}
  • Hardware and Software Resource Requirements {~1/2 page or less}
  • Preliminary Schedule (Task Budgeting) {~4 pages including diagrams}
  • Appendices
• Details
  • Here is a more detailed outline of a contract, using the hierarchical numbering, etc. As always, if you think you have a good reason to do so, you may of course deviate from my example.