Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Spring2004 M3 - Design the whole thing
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). We are requiring the use of ECoDE for your designs. All the information on ECoDE including download and manual information can be found here: Spring 2004 Ectropic Design. ECoDE supports object-oriented analysis, object-oriented design, and code generation/importing. You can save your design (.ect file) in order to turn-in much of your design for this and all the remaining milestones. The following is what you should turn in:
- An ECoDE (.ect) design containing
- CRC Card analysis for the ENTIRE system (through M6)
- SCENARIOS that touch on all major functions of the assignment from the user's point of view. See About Scenarios
- The design-time, UML class diagram for the ENTIRE system. This diagram only implements a subset of the UML, but you can model the core features by tightly integrating design-time concepts with your analysis.
- Other documents (.txt, .doc, or .pdf format)
- 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 (.ect design and .txt/.doc/.pdf materials) should be turned in on the cs2340turnin coweb: http://coweb.cc.gatech.edu/cs2340turnin. This file should be submitted to the coweb before class (noon) on March 2, 2004.
- 15% ECoDE CRC CARDS representing a good behavior analysis: Reasonable names, understandable and clearly defined responsibilities, useful comments.
- 15% ECoDE SCENARIOS (About Scenarios) described 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% ECoDE UML CLASS DIAGRAM reflecting your analysis and design in ECoDE.
- 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%).
- 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.
- 10% 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?
- 10% 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 Spring 2004 Milestone 3
Links to this Page