Each team has to turn in a print-out of a draft of their analysis class diagram, and has to be prepared to discuss it in class. After this assignment has been turned in, the draft will be revised and will become the core section of the Milestone 2 Document.
The draft contains all the classes needed to model the requirements. If the requirements document is incomplete, it has to be completed. All the appropriate associations between the classes must be shown. All multiplicities that are not "1" or "0..1" must be shown. If there is more than one association between two classes or if the purpose of an association is unclear, it must have a role name at each navigable end. Do not use the verb phrase notation for associations. Generalizations must be shown if appropriate. Attributes and operations should be shown if they are helpful for understanding; if they are clearly part of the requirements, they must be shown. Notes and property strings can be shown if helpful. The purpose of each class must be clear; if its name, attributes, and operations do not make it clear, an explanation in natural language must be given.
The class model can be split up into several diagrams, if so, each diagram must have a title. A class may have to be shown in more than one diagram if necessary for understanding. Lay out the diagrams so that they are readable.
Please bring a digital version of your diagrams, so that they can be projected on the big screen if needed. You should have a way to display your diagrams in a UML tool.
Note: All the projects in this class are different. If something in the milestone requirements does not work well for your project, please talk to the instructor, and we may arrange changes to the milestone requirements.