Create class diagrams to display the structure of the classes in the hotel system.

The Class diagram is the main analysis/design diagram for a system. The class diagram describes: the identity of the system, its relationship to other classes, its attributes, and its operations. Class diagrams model static behavior.

The class diagram is developed in an iterative fashion, in other words, through a repeated cycle of analysis, design, and implementation.

Often issues that affect the design arise during implementation. Changes made to implementation code need to be reversed in the analysis model so that iterative design can continue. System Architect facilitates this process by enabling you to implement the design in C++, Java, and Visual Basic. System Architect can then reverse that code back into the existing class diagram, which automatically updates the information stored on the diagram and in the encyclopedia.

After completing the lessons in this module you will know how to:

This module should take approximately 20 minutes to complete.

If users need to download data or prepare their environments before beginning the module, provide instructions for how to do this. If module prerequisites deviate from tutorial prerequisites, acknowledge this.

Create a new UML class diagram and add existing classes to the class diagram.

Build relationships between classes by adding an association line.

Define the associate you made between the Diary and Reservation class.

Add association lines to other classes in the diagram.

Build a straight, any orientation line to illustrate the options of a customer making a reservation on business.

Run a Microsoft Word report to verify that every message modeled between objects on a sequence diagram has a corresponding association between the instantiated classes, (and vice versa).