General Comments on the Exam

in the past, the exam corresponds to the content of assignments very closely
this year's exam may have a different format and you should ask the prof. for more on that
some hints and marking guidelines to the April 2002 exam

April Exam 2002 - Hints

provide both class diagram(s) and use case diagram
classes (in the order of appearance): customer, package, office, location, who (dropped off), city, clerk, representative, route, start/end point, distribution center, mode of transport, vehicle identifier, person (sign)
use cases: get information about, delete a previous shipment, enquire, query the estimated time of arrival
general marking comments on OOA:
- completeness: all artifacts must be modeled, cadinality of relationship
- don't contain any design, and correspond closely to the text
- clarity in UML diagram
- no operation needed
- model the domain, not the software operations

- a simple OOA required and only involves class diagram, this information is scattered, classes: people, relationships (not commands)
- the table is mostly part of the OOD
- design patterns that can apply include:
- prototype/builder (load new commands),
- composite (family tree),
- command,
- singleton (central data entry),
- builder/prototype, iterator, interpretor (married-to)

functional, high level use cases: obtain package (pickup, dropoff), route, notify, receive, query/enquire
logical view: UML package diagram and dependencies
process view: real time vs. batch (need to be decided)
deployment view: distributed server (for "different structure and technology upon...")