ONLINE HOTEL MANAGEMENT SYSTEM

N.Abisha
ABSTRACT
The mission is to facilitate easy management and administration of a hotel with capabilities to do Booking or reservations of the rooms, Cancellation of the rooms, Cash billing, Room service, Restaurant service, Restaurant billing, Total billing, and Travel arrangement using the automated hotel management software. One can keep detailed records or info on an unlimited amount of customers. The system lets the user know which all rooms are available for occupancy at any point of time. This makes the booking considerably faster. And thus helps the hotel in better management and reduce a lot of paper work as well as manpower. Index Terms: Automated Software, Feasibility Study, UML diagrams. 1. INTRODUCTION Hotel Management System is a software system where the management of entire hotel is computerized. In this project the details are maintained like customer details, reservation details, Booking details and billing details The reservation process of reserving rooms for the customers, canceling the reserved rooms, booking the rooms , vacating the rooms, the restaurant management, billing process, etc all are computerized and the management is done without any difficulty. The reports can be viewed completely and the head of the management daily or weekly or monthly can review it. For company auditing it will be more useful. This Proposed System will be interactive, faster and user-friendly for the end users. Using the hotel management system, the following activities can be performed.

A.Bharathi

R.Divya
Booking or reservations of the rooms Cancellation of the rooms Cash billing Room service / Restaurant service Restaurant billing Total billing Travels arrangement

2. LITERATURE SURVEY 2.1. STUDY ON EXISTING SYSTEM Hotel Management involves maintaining various operations of the hotel like Booking or reservations of the rooms, Cancellation of the rooms, Cash billing, Room service, Restaurant service, Restaurant billing, Total billing, Travels arrangement etc. The existing system is a manual one and there is lot of issues like erroneous data, slow process, lack of security etc. Finding out the final payment amount completely relies on the hotel manager and if he is absent, it takes a long time to find out the details during check out and is prone to errors. 2.1.1. DRAWBACKS OF EXISTING SYSTEM THE

Manual entry consumes more time. It is difficult to maintain bulk of record in manual. Restrictions in the users. Not easy to prepare the daily reports. Lack of accuracy and error prone. Overall efficiency is less. Lot of paperwork. Non-secure. No perfect maintenance of report. No method to trace details

Human errors The manual system is too slow Searching is more time consuming

Hotel Receptionist. Hotel Administrator.

2.2. PROPOSED SYSTEM The proposed system is to facilitate easy management and administration of a hotel with capabilities to do Booking or reservations of the rooms, Cancellation of the rooms, Cash billing, Room service, Restaurant service, Restaurant billing, Total billing, Travels arrangement etc. using the automated hotel management software. 2.2.1. ADVANTAGES OF PROPOSED SYSTEM The following are the objectives and highlights of the proposed system 3. Secure data Faster process Error Free Better management Save a lot of manpower Can easily make the daily reports Elimination of Paper work. High reliability and security. Fast and economical. Maintains large Terabytes of data. UML DIAGRAMS

3.1.1. INQUIRE INFORMATION The customer needs to interact with the hotel interface through the personal system. It involves set of actions. 3.1.2. RESERVE/UPDATE RESERVA TION To reserve the room, the customer needs to interact with the website. If the customer already reserved room, want some updates regarding the increase in occupancy, he must able to update the data by using his login and password which can be provided by the administrator. 3.1.3. PAY FOR HOTEL This involves set of actions. If the customer ready to book or reserve the room, he needs to enter his complete details and occupancy level. After furnish the details in the form, he demanded to pay the advance. That can be through credit card/debit card. He must enter the correct card number. 3.1.4. CANCEL RESERVATION The system software should support all the requests made by the each authorized customer. If the customer not satisfied with the facilities and occupancy of each room after few hours he checked in, he may want to cancel the reservation for remaining hours. System software must be in a position that the payment for the staying hours should captured and cancel the reservation. 3.1.5. UPDATE HOTEL INFORMATION According to the customer feedback, the administrator is updating the hotel information such as offers, discounts on rooms and meals provided by the hotel. When the customer checkout from the hotel, the database needs to update and show the availability to the new customer.

3.1. USE CASE DIAGRAM A Use Case specifies the behaviour of a system or a part of a system and is a description of a set of sequences of actions. Use case diagram shows the relationship among use cases within a system or semantic entity and their actors. The relationships are associations between the actors and the use cases, generalization between the actors. Actors in Online Hotel reservation System: Client. Travel Agent.

3.1.6. RETURN PAYMENT This use case extends cancel reservation. Whenever the customer wants to cancel the reservation, system must cancel the reservation and return the payment which remains. Each and every transaction made by the customer or administrator must be updated with the customer database and room database. This is the brief explanation about the Use cases in the hotel reservation system which helps in modelling the dynamic aspects of the system. Generalization relationship exists between hotel receptionist and hotel administrator. The relationship between them is like child and parent relation. Here Administrator assumes as a parent whereas Receptionist acts as a child.

3.2.2.

Room Rate: Hotel. Room Type. Employee. Travel Agent. Hotel Booking. Room. Room Booking. Person. Client. Credit Card. INTERFACES FOR RESERVATION SYSTEM .Booking is an interface which can be declared to provide the operations such as doBooking(), cancelBooking() to the classes Employee, TravelAgent and Client where the implementation of those methods can be done. Here the relationship between the class and interface is the realization where classes realize the interface such that the interface gives the contract and the classes need to carry out that work. This is the brief description about the class diagram and the classes, interfaces declared for the online hotel reservation system.

3.2. CLASS DIAGRAM Class diagrams are the most common diagrams found in modelling object oriented systems. A class diagram shows a set of classes, interfaces, and collaborations and their relationships. This gives the static design view of the system. 3.2.1. CLASSES DECLARED FOR RESERVATION SYSTEM Facility.

3.3. SEQUENCE DIAGRAM Sequence diagram is an interaction diagram that shows how operations are carried out, what messages are sent and when. Sequence diagrams are organized according to time. Here the sequence diagram shows the making of hotel reservation where the object initiating the sequence of messages is a Reservation window. The reservation window sends a makeReservation() message to a HotelChain. The HotelChain then sends a makeReservation() message to a Hotel. If the Hotel has available rooms, then it makes a Reservation and a Confirmation. Here reservation equivalent to the term Booking. In the diagram, each vertical dotted line is a lifeline.

Representing the time that an object exists .Each arrow is a message call .An arrow goes from the sender to the top of the activation bar of the message on the receivers lifeline. The activation bar represents the duration of execution of the message .In our diagram, hotel which is requested for booking of the room through makeReservation, issues a self call to determine if a room is available .If available, the hotel creates a Reservation and a Confirmation. The asterisk on the self call means iteration.

State chart Diagram: State chart diagrams are for modeling the dynamic aspects of the system.A state chart diagram shows a state machine.State chart diagram is useful to model the life time of an object. And itshows the flow of control from one state to another state. State Machine: A state machine is a behavior that specifies the sequences of states anobject goes through during its lifetime in response to events. State:

A state is a condition or situation in the life of an object during which itsatisfies some condition, performs some activity, or waits for some event. Event: An event is the specification of a significant occurance that has a locationin time and space.State chart diagram commonly contains: Simple states and composite states. Transitions, including events and actions. Diagram Description:

From the diagram which is for reservation of room in a hotel, it is clearthat there is a transition from the idle state to composite state.Composite state is a state in which again the object undergoes differenttransitions throughout its life time.Whenever the customer interact with the window interface and make arequest for reservation, then the object states changes from idle tocomposite state. In composite state, the object moves from one state to another until thecustomer reserved room by paying some amount in advance.Once the room reserved, then the reservation letter may send to thecustomer mail id by moving its state to transmitting. 15 Once the room reserved by the customer, then the object comes to theidle state again by coming out of the composite state.This is the brief description about the state chart diagram for the hotelreservation system. 16