Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Fall 2004 M3
Time to design the whole project...
Teams must turn in a detailed design and group plan THROUGH THE REST OF THE CLASS (i.e., through M6). The following list givs the details of what you should turn in:
- SCENARIOS that touch on all major functions of the assignment from the user's point of view. See About Scenarios
- CRC Card analysis for the ENTIRE system (through M6)
- A UML class diagram for the ENTIRE system.
- UML sequence diagrams that illustrate the operation of the following functions of your system:
- interaction between two persons
- interaction between a person and an object
- movement of a person to a new location
- the basic simulation mechanism you use.
- A TEST PLAN corresponding to the CRC card analysis, based on your scenarios and exceptional variations. See About Test Plans
- Team member roles - description of what each team member is going to be responsible for.
- Internal group timeline with dates, responsibilities, and milestones.
We expect the design to evolve over the following weeks, but we want to see that you've thought through everything UP FRONT.
A single zip file containing all your design documents should be turned in on the cs2340turnin coweb: http://coweb.cc.gatech.edu/cs2340turnin. This file should be submitted to the coweb before class (1:30) on October 14, 2004.
- 15% SCENARIOS constructed from specific examples that touch on every major function in the system from the user's point of view.
- Clear descriptions for each scenario are written for a non-computer-science audience (10%).
- Good assignment of responsibilities impelemented by CRC Cards that satisfy each scenario (5%).
- 15% CRC CARDS representing a good behavior analysis: Reasonable names, understandable and clearly defined responsibilities, useful comments.
- 15% UML CLASS DIAGRAM reflecting your analysis and design.
- A quality design covering all the features of the project (10%).
- Detailed and understandable names and comments (5%).
- All the classes are connected with responsibilities (5%).
- 10% UML SEQUENCE DIAGRAMS for the functions listed in the requirements.
- 20% Quality of the design.
- Covers all the functionality (10%).
- Clear, concise, robust, and correct design - effective distribution of responsibilities (no god classes or classes without function), high cohesion, and low coupling (10%).
- 15% TEST PLAN (About Test Plans) with clear linkages between scenarios and test cases and expected results. We should be able to verify that your test plan covers all of the system requirements.
- 5% TEAM MEMBER ROLES. A clear definition of what each team member is responsible for: Can you tell who will do which pieces of system (as defined in your design)? Will you be able to figure out whose part failed if there's a failure?
- 5% TIMELINE. A believable and detailed group timeline: Can a team member figure out from this what they're supposed to be doing each week?
Questions on Fall 2004 M3
Link to this Page