CS 50, Winter 2010

1. Update the project description you prepared for assignment 1 to make sure this description is still an informative introduction to your proposed project.
2. Prepare a Vision (see Larman chapter 7), including at least the following sections:
   • Problem statement
   • Key high-level goals and user goals (okay to combine to one section)
   • System features
   • Other requirements and constraints (enhanced, with details that might appear in the "Supplementary Specification" of a more elaborate project).
3. Identify, and write use cases (see Larman chapters 6 and 30) for the proposed system. Use an "essential UI-free style" (section 6.11) and include at least the following sections:
   • Name of use case
   • Primary actor
   • Main success scenario (basic flow)
   • Extensions (alternative flows)
   Use case diagrams are not required, but would be helpful if there are many use cases and/or important relations between use cases.
4. Prepare a schedule for implementing the use cases over at least two development iterations. Say which use cases will be fully implemented in the first iteration. If your intention is to implement simplified versions of any of the use cases in iteration 1 (and complete them in a later iteration), describe the simplified use cases.
5. Begin a glossary (Larman section 7.9).
6. Assemble a complete requirements analysis document. All text must be typewritten (but hand-drawn diagrams are acceptable). The document must be assembled in the following order, and attached by a single staple in the upper left corner:
   1. Cover page with group identification code (see table on Project page), project title, each of your names and e-mail addresses, and your TA's name.
   2. Project description
   3. Vision
   4. Use cases
   5. Project schedule
   6. Glossary
7. Turn in the document as directed by your TA. Officially, it is due Friday, January 22 by 5:00pm. Credit may be reduced up to 30 percent per day for late submissions.

Updated January 9, 2010, by C. Michael Costanzo