CS 50, Winter 2010

Work scope

• Plan precisely how much more of the system will be completed before the project deadline, and meet with your TA to discuss your plan.
• Perform these activities for each additional iteration:
  1. Synchronize key analysis and design artifacts to the code produced for earlier iterations. (Be sure to do this after the last iteration too.)
  2. Analyze and Design. Create or update the following items:
     • static class and package diagrams
     • system sequence diagrams and related operation contracts (just for system operations)
     • interaction and statechart (state machine) diagrams
  3. Implement and Test. Be sure to update the javadoc comments too, and post them online.

Deliverables - All must be done by 5:00pm, Friday, March 12

1. Demonstrate the final system to your TA. Schedule an appointment with her first.
2. Turn in printed documentation, neatly bound or stapled (or as a single PDF file), as instructed by your TA.
   

   Include the following items in the order shown - any specific artifacts listed below are required - and add sufficient text to tie the parts together (i.e., make it seem like a final report).

   • Title page - the usual data, and other decoration as desired
   • Table of contents - just a guidepost; no page numbers necessary
   • Project description - and introductory text
   • Vision - do not include use case text (but diagrams are okay)
   • Analysis and design - package and static class diagram(s), system sequence diagrams, key interaction diagrams, and key statechart diagrams
     

     Select artifacts that (together) show your system's internal features, and arrange them to clearly communicate these features to the reader.

   • Glossary - updated and cleaned up as necessary to reflect the final system
   Special note: we will keep this documentation for our records. Make your own copies before turning it in.
3. Turn in the source code and an executable jar file - including any required data, graphics, or other files necessary to execute the system. These files must be physically arranged as specifed in the assignment 4 instructions (item 5), including an up-to-date README.txt file. The updated URL where your javadocs are posted should be included in README.txt too.

• Late projects (or parts thereof) will be docked points at the TA/Instructor's discretion.

Updated February 19, 2010, by C. Michael Costanzo