CECS 332: Project Specification Document

Due Friday, Sept. 26, 5 p.m.

Submit one copy per group via WebCT

Use the outline below:

1. Table of Contents
2. Introduction
• Include the basic idea and the motivation for the project
3. Glossary
• Define special terms, especially domain terms
4. User requirements definition
• A high-level description for users in paragraph or bullet form
• Expand your problem statement
• Include functional and non-functional requirements
5. System architecture
• Context diagram showing how your system interacts with its environment
• (Optional) block diagram of your system
• Include a brief description of each block
6. System requirements specification
• A more technical description in paragraph or bullet form for the software developers
• Include functional and non-functional requirements
7. System models
• Use case diagram
• For each use case, include the starting and ending conditions, the sequence of steps and the exception handling
• Include other models as appropriate for specifying functionality
8. System evolution
• (Optional) projected maintenance requirements
9. Appendices (if applicable)
10. Index (optional)