You will continue your design by moving from the Domain-level model to the actual application design.

M5 Requirements

• Create your Software Architecture and Trust Boundaries
• Identify your Application and Utility Objects (those new objects specifically developed for the design. You do not have to say which are which, just id the ones that were added from the domain analysis)
• Add necessary CRC Cards and any new scenarios needed (for newly discovered domain classes if any)
• Submit a UML Class diagram of your refined design (shows all domain and application/utility objects)
• 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.
• Submit a written contract (1 per person on the team) for an object or method in the design
• Submit a short paragraph on your error handling and exception handling design strategy.

Although not required, it is recommended you have begun some implementation of basic Domain Model objects.

Criteria Breakdown:

• Architecture/Trust Boundaries.............. 10
• Application/Utility Class Identification .....10
• Updated CRC Cards...............................5
• Updated Scenarios................................5
• UML Class Diagram...............................20
• UML Sequence Diagrams.......................20
• User Interface Screen Prototypes...........15
• Contract .......................................... 5
• Exception Handling Strategy ................ 5