Class Diagram Building on your functional models (use cases and activity diagrams) and object identification techniques in Chapter Five: Object Identification, create 1 class diagram to represent the structural model of your system.
The class diagram should include major classes in your system and the associations between them. Include attributes, operations/methods, and detailed information about association relationships (generalization, aggregation, composition). You needn’t include every kind of association, but do consider whether they are appropriate for your design. See Figure 5-7 in your book as a guide.
I recommend each team member come up with at least one class and draft the attributes and operations for that class. Then pull all your classes together as a team and discuss their relationships, areas of overlap, etc.
Before submitting any of your diagrams, validate them! Walk through them with one another to make sure they communicate what you want them to.
TIP: Microsoft Visio has a library of shapes specifically for UML Diagrams. In the left-hand Shapes box, click on "More Shapes >> Software and Database >> Software. There is a collection of pre-set shapes for each type of UML diagram we draw.