Introduction: UML modeling for information system architecture
Apply the Use Case approach to design part of a hotel reservation system. Begin by analyzing Use Cases, then model with Sequence and Collaboration diagrams, and then build a simple UML Class diagram. Lastly, model the dynamic behavior of one of the classes in the system using a State diagram.
The Unified Modeling Language (UML) has become the standard notation for modeling object-oriented and component-based systems. UML is a language not a method–it provides a specification for a standard set of symbols to represent object-oriented systems and concepts, and a specification for the underlying semantics–clearly defining what the symbols mean and how they are related. It is not a method because it does not specify how to build systems.
Use Case Driven method
There are a number of methods for developing object-oriented and component-based systems with UML. Most popular UML methods (including RUP and Iconix) adhere to a Use Case-driven approach. In general, the Use Case-driven approach involves beginning analysis by trying to capture the problem at hand using Use Case diagrams. Use Cases are used to capture each scenario in the existing system or in the system to be built. Each Use Case is then decomposed by Sequence and/or Collaboration diagrams to model the objects that make the scenario work.
Build a simple sequence diagram to illustrate the relationships between objects in your Use Cases. Buid a collaboration diagram to see more detail about how objects in a sequence diagram relate.
Create a state diagram to show the events that cause a transition from one state to another state, in a class. Build a state diagram for the Reservation class.