1. Design Model: Specification View (40 points)
a) One or more class diagrams showing all the classes in the system and all of their relations. Classes
from libraries or frameworks that are used must also be shown; but only those of their relations that link
them to classes of the project. Reused classes must be clearly shown as such. Operations and attributes do not need
to be shown in this view.
b) A package diagram showing the subsystems and their dependencies. If large libraries are used, each of those
should also be shown as a subsystem.
c) A discussion of the architecture used. For most projects this will be the three-tier architecture; explain
how your subsystems fit into this architecture.
2. Design Model: Implementation View (50 points)
a) A model of each class, including a description of its purpose, and a list of all attributes and operations.
Operations that are not obvious must be described. For each class, it must be stated to which subsystem it belongs.
b) Interaction and state diagrams as needed. Minimum: four diagrams.
3. Updates (10 points)
a) An updated project schedule.
b) Updated requirements and analysis models, as needed. All models must be consistent.
c) Updated table of use-case realizations, now including both analysis classes and design classes.
If adjustments to these requirements are necessary due to the nature of your project, please contact the instructor. The milestone will be graded based both on correctness and completeness.