View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Flat Circle Society Cases

Overall suggestions

M1:
• Form a 3-4 Person Team
• Identify Domain classes
• Create CRC Cards and Scenarios for the Candidate classes
• Assign Role Sterotypes and Responsibilities to classes
• Roleplay scenarios to clarify responsibilities and collaborations
• Meet with your assigned TA (after submission grading) to discuss your design and possible improvements

What worked?

What didn’t work?

What could have been better?

M2:
• Create your Software Architecture and Trust Boundaries
• Identify your Application and Utility Objects
• Add necessary CRC Cards and any new scenarios needed
• Submit a UML Class diagram of your refined design
• Submit 2 UML Sequence diagrams that shows your full design handling one or more scenarios
• Submit screen mockups that show your preliminary user interface. These screens can either be hand-drawn, or prototyped with the VW Painter and then captured.

What worked?
What didn’t work?
What could have been better?

M3:
• Implement Domain Objects
• Implement basic UI screens to input data
• Create SUnit tests to unit test your core Domain Objects

What worked?
What didn’t work?
What could have been better?

M4:
• When a scenario is selected for roleplay, the cards display graphically on the screen, and arrows move from responsibility to responsibility showing the flow through your classes.
• When a UML diagram is requested, display a simple UML diagram showing the classes, and their relationships (limited to inheritance or basic association).
• There is no requirement for fancy layout support.
• There is no requirement to support full UML (interfaces, aggregation, etc.)

What worked?
What didn’t work?
What could have been better?

M5:
What worked?
What didn’t work?
What could have been better?

Link to this Page