Hotel Reservation Management System - Case Study Example

Object Oriented Analysis and Design through UML Diagrams Hotel Reservation Management System Object Oriented Analysis and Design through UML DiagramsUnified Modeling Language Diagrams are a series of diagrams used to fully represent an IT system. Different diagrams are used to represent the system in different viewpoints. The major UML diagrams are: Use Case Diagram: This represents the system as a group of Actors and Use Cases. Here, actors are the people or external entities that use the system. Each action an actor can perform is called a use case. Class Diagram: A system can be segregated as a group of classes. Each class is an independent logical unit in the system. Classes have relationships such as direct dependency, aggregation, generalization etc depending on how the classes interact together. Sequence Diagram: Sequence diagrams represent a system’s behavior over a time series. State Chart Diagram: This diagram is used to represent the different states a system transitions into. Activity Diagram: As the name represents, this diagram is used to represent the system as a series of activities and actions. Requirements Description A Hotel Reservation System is essentially a software program, to automate the entire vertical of Hotel Reservation from end to end. It starts with the customer placing a call or personally arriving at the front desk of the hotel, to successfully placing the order. It is evident that there are two interfaces to this system. One internal facing; relevant to hotel management activities such as Room Maintenance and the other is the external interface; relevant to the booking activities. The series of activities for booking a hotel room end to end are as follows. Customer places a call to the receptionist. Receptionist greets and takes customer’s demographic information. Receptionist takes the dates for which the room is required. Receptionist takes the room requirements. Receptionist checks for availability of customer’s specific rooms for the dates mentioned. If room is unavailable, Receptionist suggests alternative date / room combination. If customer is not satisfied, the order process is terminated. If customer is satisfied, then proceed. Once customer is satisfied, the receptionist prepares the bill. If price is not agreeable to customer, Receptionist suggests other alternatives. If customer is not satisfied, the order process is terminated. If customer is satisfied, then proceed. Once the customer is satisfied, receptionist books the room. Customer is invoiced. The other internal activities include the following. Maintain Customer Master Data Room Maintenance Room Service Use Case Diagram A Use Case diagram represents the Actors and their Use Cases. Actors in essence are all the external performers who interact with the system. Use Cases are all the actions performable by each Actor. The connector in between the Actor and his Use Cases are called associations. The Actors of the Hotel Reservation System and their Use Cases are listed below. Actor Use Cases Hotel Manager Login Maintain Booking Record Rooms to be maintained Supervision over receptionist Check Customer Database Hotel Receptionist Login Receive Customer Call Specify Room Specification Check Room Availability Book Rooms Perform Billing Maintain Booking Record Rooms to be maintained Customer Make Call Specify Room details Specify Dates Billing Booking The following is the Use Case Diagram for the Hotel Reservation System. Class Diagram A Class Diagram represents the system in terms of classes of a system. Each class is a logical unit that has some attributes and performs some actions. The lists of classes for the Hotel Reservation System are: Hotel Room Customer Hotel Manager Hotel Receptionist Class diagrams also represent Interfaces. Interfaces are similar to a Class except for the fact that an Interface acts as a unit that assists the main classes in their operations. The interfaces for the Hotel Reservation System are: Customer Database Reservation System The following is the Class Diagram for the Hotel Reservation System. State Chart Diagram A State Chart diagram represents the various states the system transitions into throughout the process. An action triggers a state and a system remains in that state until another action transitions it to another state. The following is the State chart diagram for the Hotel Reservation System. Activity Diagram An activity Diagram represents the system in terms of all the activities that happen in the system. This is like the end to end sequential processes a system performs. The following is the Activity Diagram for the Hotel Reservation System Read More