Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
M5 Team Smalltalk
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) This should be easy, as all classes that were not identified with a CRC card will be in this category. You can annotate them on the class diagram, or you can list them separately. These are all the classes that don't fit into the domain, like data structures, network and thread classes, database access classes, UI classes, data validation classes, and any other classes necessary for this to run on a computer, but are not really part of the domain itself (and thus don't have CRC cards).
Add necessary CRC Cards and any new scenarios needed (for newly discovered domain classes if any). If you have no new classes, and nothing to fix from your TA meeting, then you may not have anything for this point. In that case you will receive the points for "free" as a reward for doing a good job the first time.
Submit a UML Class diagram of your refined design (shows all domain and application/utility objects – you do not have to show constructors/getters/setters unless you need them for the sequence diagram)
Submit 2 UML Sequence diagrams that shows your full design handling one or more scenarios. You should make your scenarios interesting so these diagrams help you.
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 a method in the design. Remember that the contract is basically the pre and post conditions of the method and the signature (the name, parameter list and expected types of the parameters).
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.
Again a fairly straight forward assignment without any coding. Just pop open VP and get started. I have attached our work:
The contracts are a bit off, but this is what we turned in at that point in time:
assignments: x y where addAssignments is a private instance of user class and x is any student and y is any course.
- Precondition: student x must exist and course y must exist
- Postcondition: Assignment is available for editing or removal.
assignments: x where removeAssignments is a private instance of user class and x is any student.
- Precondition: student x must exist.
- Postcondition: Assignment is now unavailable.
Take in mind this was just a milestone and our GUI changed drastically before the end.
Link to this Page
- Team Smalltalk last edited on 5 May 2010 at 6:52 pm by c-67-191-182-51.hsd1.ga.comcast.net