HOTEL MANAGEMENT SYSTEM

INTRODUCTION OF ONLINE HOTEL MANAGEMENT SYSTEM:

Are you looking for Online hotel management system for your final year project? We are here to help you. You can contact us

The project Online Hotel Management System is a web based application that allows the Hotel Manager & Owner to handle all hotel activities online easily and safely. Using Interactive GUI anyone can easily learn to use the complete system.

Using this Hotel Manager don’t have to sit and manage the entire activities on paper. And at the same time Owner of the Hotel will feel comfortable to keep a check on Hotel easily from anywhere around the world.

This System will give them power and flexibility to manage the entire system from a single online portal.Hotel management System provides room booking, staff management and bill generation features.

The system will be so simple and attractive which will make the customer comfortable to use and choose their ideal room.The system allows the Owner to check the Progress of the hotel from interactive Graphs and he will be notified of each new change made in System.

The system allows the manager to keep track on available rooms in the system and even maintain staff details like their hours worked and salary.

Customers can view and book an available room online and the system will automatically generate the bill according to the number of days the type of room is booked.

MODULES OF ONLINE HOTEL MANAGEMENT SYSTEM:

There are several modules required to complete this system. Here we are discussing the main modules or core modules of the system.

OWNER PROFILE:

In Owner profile, he has full access to the system. The owner can view all the details in a graphical way and he has the authority to change the Cost of Room, Room Availability, Service Details and much more.

He can also check the details of receptionist and staff member currently working at that Hotel. He will get the notification of all the changes made by the Manager in the system.

He will also have special permission to revert those changes if needed. He can also check the transactions made through the day and thought the month and an algorithm will check the progress the Hotel is making.

MANAGER PROFILE:

Manager profile can have partial access to the System. The manager can view the availability and can change the cost of room and other service details. He will also have a special interface where he can manage the staff of the hotel.

He can add new people and he can also remove anyone from the system. And at the same time Owner will receive the notification of these changes.

CUSTOMER PROFILE:

In Customer profile, people can check the availability of rooms and they can also book a room according to their budget and need.Customer profile contains their name, Contact details, address, and other necessary details etc.

They need to sign-up for booking the hotel, which will make them as well as manager of the hotel to easily interact with each other. They can pay the amount Online and if they need to do payment Offline they must give some advance amount to confirm their room.

RECEPTIONIST PROFILE:

In Receptionist Profile, who so ever is the Receptionist he must log-in and then he can book the hotel for the customer and this will serve the customer as offline mode.

When he will log-in his attendance will be taken and it will be easy for Manager and Owner to monitor them. Here they will also get a notification of booked room so that they can beforehand maintain the room.

STAFF PROFILE:

In staff profile, there will be complete details of each staff of the hotel like their personal details and their post at the hotel. They can easily give their attendance to the receptionist and that attendance details will be visible in Real-time to Manager.

BOOKING:

The customer can easily search their Room from the various option available.This all will be so user-friendly so that Customer will not find any trouble in the booking room.

Once the room is searched and the customer finds his choice room then this module helps the customer to book the room by following the rules of the Hotel like Check-in and check-out time of the Hotel, Limit of people per room etc.

If everything is done properly he will be asked to pay partial or complete money. And then he will be forwarded to Payment Gateway. Where he can easily pay Online.

PAYMENT DETAILS:

After filling the booking details clients need to pay the money using different options available like cash/net banking/ATM card. Payment portal would use a payment gateway to clear payment.

Once payment will clear receipt of payment will be generated automatically and this receipt will be sent to manager and Receptionist will get the notification to make the room ready before they arrive.

ADD / UPDATE / DELETE HOTEL MEMBERS / BOOKING DETAILS:

Owner and Manager can easily add, update, or delete the Staff details.If the customer does not reach the hotel within 3hr of check-in time and if he does not give any prior details of this arrival then receptionist will have complete authority to remove his booking and allow another customer that room if needed.

USER AUTHENTICATION ACCORDING TO HIS/HER ROLE:

This portal will take care of every profile is our system. No user will be allowed to use our system without a valid ID. Every profile must authenticate using system procedure. This would ensure the security of our system.

SYSTEM DESIGN OF ONLINE HOTEL MANAGEMENT SYSTEM:

This complete System run on the simple Interface was there are only three users i.e. Owner, Manager, and Customers.

THE CASE OF CUSTOMERS OF ONLINE HOTEL MANAGEMENT SYSTEM:

The customer can view the Availability of Room in Hotel. If he wishes to book he has to sign-up by providing his contact details and then a user ID will be generated using this he can securely enter the System and then he can book and Pay Online with full security.

He can also change his check-in time and check-out time if possible.He can also cancel the booking if he doesn’t wish to visit.

THE CASE OF RECEPTIONIST OF ONLINE HOTEL MANAGEMENT SYSTEM:

The receptionist will check all the details of Customer check-in and check-out date and time and settles any pending payments. And He will have authority to allow Room number to Customer on their arrival. He will take care of all customer needs and their comfort.

THE CASE OF OWNER/MANAGER OF ONLINE HOTEL MANAGEMENT SYSTEM:

The owner, as well as the manager, has almost the same Authority. Both can see all the details of the hotel and can Change. The manager can change details but Owner will receive the notification of any changes made by him.

So that it will be easy for the Owner to keep track on his hotel even if he is far away. This all will take place securely since both Manager and Owner will have separate IDs and whatever they will do all will be fully secure in this system.

USER INTERFACE(UI) OF ONLINE HOTEL MANAGEMENT SYSTEM:

The user interface is very important part of the system. This helps every member of the system to interact with each detail properly. As we have shown several use cases in this system.

We have developed these interfaces to interact with the system.

LOGIN PAGE:

Owner or Manager need to log in using login id and password.

CUSTOMER PAGE:

Can view their details as well as Booking details.

RECEPTIONIST PAGE:

He can Offline Book the available room at the hotel.

PAYMENT PAGE:

This interface helps in paying the money via several modes.

ER-DIAGRAM OF ONLINE HOTEL MANAGEMENT SYSTEM

There are mainly Seven Entities Owner, Manager, Employee, client, hotel, Payment, book. These five entities would manage the whole system. There are mainly Seven Entities Owner, Manager, Employee, client, hotel, Payment, book.

These five entities would manage the whole system.

OWNER:

The owner is a super user of the system. The owner is just like admin. The owner has all right to view and modify the data in the system. The owner has followings attributes.

OWNERID:

This is numeric 14 digits number which is unique to every admin. OwnerID is the primary key to admin table in the database.

NAME:

This attribute would hold the name of the owner. The name is varchar type variable which holds the data length up to 250 characters.

EMAIL:

This is an essential attribute of the table. Every owner must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

CONTACT.:

This is multi valued attributes which mean every owner can have more the one mobile number in database.

ADDRESS:

This attribute would hold the address of the owner. Each employee must provide the address.

MANAGER:

The manager is a secondary user of the system. The manager can view hotel details, manage employee, booking, solve client’s problem. The manager has followings attributes.

MANAGERID:

This is numeric 14 digits number which is unique to every Manager. ManagerID is the primary key to Manager table in the database.

NAME:

This attribute would hold the name of the manager. The name is varchar type variable which holds the data length up to 50 characters.

EMAIL:

This is an essential attribute of the table. Every Manager must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

CONTACT.:

This is multi valued attributes which mean every manager can have more the one mobile number in database.

ADDRESS:

This attribute would hold the address of admin. Each employee must provide the address. Admin address is verified via Human resource team.

EMPLOYEE:

The employee is another user of the system. An employee can view hotel details, verify the online booking room availability for clients. The employee has followings attributes.

EMPID:

This is numeric 14 digits number which is unique to every Employee. EmpID is the primary key to Employee table in the database.

NAME:

This attribute would hold the name of Employee. The name is varchar type variable which holds the data length up to 50 characters.

EMAIL:

This is an essential attribute of the table. Every employee must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

CONTACT.:

This is multi valued attributes which mean every employee can have more the one mobile number in database.

ADDRESS:

This attribute would hold the address of the employee. Each employee must provide the address.

CLIENT:

The client is the basic end user of our system most of the business is done through them. Clients would book the desired hotel room. The client would provide the feedback. The client has following attributes.

CLIENTID:

This is numeric 14 digits number which is unique to every Client. ClientID is the primary key to client table in the database.

NAME:

This attribute would hold the name of clients. The name is varchar type variable which holds the data length up to 50 characters.

EMAIL.:

This is an essential attribute of the table. Every client must have a working email id. This field has validation only email formatted values will be stored.

ADDRESS:

This attribute would hold the address of clients. Address of clients would help us to connect with them and visit the location. This would provide better services.

HOTEL:

Every hotel registered with the system has the information in this entity. Hotel is the main concern of system.

HOTELID:

This is numeric 14 digits number which is unique to every Hotel. HotelID is the primary key to case table in the database. Each hotel is uniquely identified using this id.

NAME:

For customer point of view, every hotel does have its name. The name is very important.

NO OF ROOMS:

Every hotel has many rooms. To make it easy for the customer. And check availability no. of rooms should be in the database.

ADDRESS:

This attribute would hold the address of the hotel. Address of Hotel would help the client to find it easy and visit the location. This would provide better services.

BOOK:

Before going to book any room. The client should check the availability. If the desired room is available. They can book it.

BOOKID:

This is numeric 14 digits number which is unique to every Booking. BookID is the primary key to case table in the database. Each Payment is uniquely identified using this id.

ROOMNO:

With reference to hotel booking must have room no.

DATE:

This would hold the date of the transaction.

PAYMENT:

Payment Entity store the data about payment. Every payment data is here. Any conflict can be resolved by looking to this.

PAYMENTID:

This is numeric 14 digits number which is unique to every Payment. PaymentID is the primary key to payment table in the database. Each Payment is uniquely identified using this id.

BOOKINGID:

This is a reference to a booking. This would help the admin to find this payment is against booking.

DATE:

This would hold the date of the transaction.

TRANSACTION NO.:

The transaction number is reference no given by the bank.

STATUS:

Status of every transaction either it would be pending or confirm is being updated in this field.

DESIGN DATA DICTIONARY FOR ER-DIAGRAM OF ONLINE HOTEL MANAGEMENT SYSTEM:

The data dictionary is useful in case of development.

Table Name: OwnerMaster

Primary Key: OwnerID

Description: To store the details of admin

Serial No.	Fields	Datatype	Description
1.	OwnerID	Integer	Primary key
2.	Name	varchar
3.	EmailID	varchar
4.	Contact.	Integer	Multiple contacts can exist for single admin
5.	Address	varchar

Table Name: ManagerMaster

Primary Key: ManagerID

Description: To store the details of General Manager

Serial No.	Fields	Datatype	Description
1.	ManagerID	Integer	Primary key
2.	Name	varchar
3.	Email	varchar
4.	Contact.	Integer	Multiple contacts can exist for single admin
5.	Address	varchar

Table Name: EmployeeMaster

Primary Key: EmployeeID

Description: To store the details of Employee Details

Serial No.	Fields	Datatype	Description
1.	EmployeeID	Integer	Primary key
2.	Name	varchar
3.	Email	varchar
4.	Contact.	Integer	Multiple contacts can exist for single admin
5.	Address	varchar

Table Name: ClientMaster

Primary Key: ClientID

Description: To store the details of Clients

Serial No.	Fields	Datatype	Description
1.	ClientID	Integer	Primary key
2.	Name	varchar
3.	Email	varchar	Multiple contacts can exist for single client
4.	Address	varchar

Table Name: HotelMaster

Primary Key: HotelID

Description: To store the details of Property

Serial No.	Fields	Datatype	Description
1.	HotelID	Integer	Primary key
2.	Hotel Name	varchar
3.	Address	varchar
4.	Number of rooms	Integer

Table Name: BookMaster

Primary Key: BookID

Description: To store the details of Payment

Serial No.	Fields	Datatype	Description
1.	BookID	Integer	Primary key
2.	Room No.	Integer
3.	Date	date

Table Name: PaymentMaster

Primary Key: PaymentID

Description: To store the details of Payment

Serial No.	Fields	Datatype	Description
1.	PaymentID	Integer	Primary key
2.	BookID	Integer	Foreign key to BookMaster
3.	Date	date
4.	Transaction No.	varchar
5.	Status	varchar