0% found this document useful (0 votes)
9 views34 pages

Sample Bishesh

Project report of hotel reservation system

Uploaded by

prasidshahi5
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views34 pages

Sample Bishesh

Project report of hotel reservation system

Uploaded by

prasidshahi5
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 34

Project Report

on

Hotel Reservation System

Submitted By:

Bishesh Sambahamphe

Roll no: 13322/21

Submitted To:

Er. Manoj Giri

September 10th, 2024


ACKNOWLEDGEMENT

It is a great pleasure to have the opportunity to extend my heartfelt gratitude to everyone who
helped me throughout this project. We are profoundly grateful to our supervisor, Mr. Manoj
Giri, for his expert guidance, continuous encouragement and ever willingness to spare time
from his otherwise busy schedule for the project’s progress. His continuous inspiration has
made us complete this project and achieve its target.

I would also like to express my deepest appreciation sir, for his constant motivation, support
and for providing a suitable working environment.

I sincerely acknowledge direct and indirect help, suggestions and feedback offered by our
colleagues before, during and after the development and implementation of this project.

Finally, special thanks go to all of my Friends who kindly extend their hands in making this
project work a success.

II
ABSTRACT

This project aims to develop a comprehensive hotel booking website for "The Star Hotel,"
providing a seamless and user-friendly experience for both guests and administrators. The
website will function as a digital gateway for potential customers to explore and book rooms,
offering detailed descriptions, images, and amenities. Guests will have the option to book
rooms with or without logging in. Logged-in users will benefit from having their credentials
automatically retrieved from the database. Additionally, the website will feature a newsletter
subscription field, where guest emails will be sent to the admin for personalized news and
promotions.

The admin panel will empower administrators to update room details, manage bookings, and
handle user data efficiently. Admins can modify room offerings, update website content to
reflect the hotel's latest services, and review booking records. Moreover, administrators will
have the ability to approve or reject bookings and manage any booked services. This platform
will streamline hotel operations, enhance user experience, and ensure a smooth workflow for
both guests and hotel staff.

3
TABLE OF CONTENTS

ACKNOWLEDGEMENT...................................................................................................................i
ABSTRACT.........................................................................................................................................ii
CHAPTER 1: INTRODUCTION......................................................................................................1
1.1 Project Introduction........................................................................................................................

1.2 Objectives.........................................................................................................................................

1.3 Problem statement...........................................................................................................................

1.4 Scope.................................................................................................................................................

1.4.1 Website Development:........................................................................................................4


1.4.2 Room Viewing and Booking:.............................................................................................4
1.4.3 Admin Panel:......................................................................................................................4
1.4.4 Content Management:.......................................................................................................4
1.4.5 Data Security:.....................................................................................................................5
1.5 Limitations.......................................................................................................................................

CHAPTER 2: REQUIREMENT ANALYSIS...................................................................................7


2.1 Finding requirement........................................................................................................................

2.1.1 Functional Requirement....................................................................................................7


2.1.2 Non-Functional Requirements..........................................................................................8
2.1.3 Use case diagram..............................................................................................................10
2.2 Feasibility Analysis........................................................................................................................

2.2.1 Technical Feasibility for Hotel Booking Website:..........................................................12


2.2.2 Operational Feasibility for Hotel Booking Website:......................................................13
2.2.3Economic Feasibility for Hotel Booking Website:...........................................................14
2.3.4 Schedule Feasibility for Hotel Booking Website:...........................................................15
CHAPTER 3: SYSTEM DESIGN...................................................................................................16
3.1 Er Diagram.....................................................................................................................................

4
3.2 Data Flow Diagram(DFD).............................................................................................................

CHAPTER 4: IMPLEMENTATION AND TESTING...................................................................22


4.1 Tools Used.......................................................................................................................................

4.2 Implementation Details of Modules..............................................................................................

4.3 System testing.................................................................................................................................

CHAPTER 5: CONCLUSION AND LESSION LEARNED.........................................................30


5.1 Conclusion......................................................................................................................................

5.2 Future Recommendations.............................................................................................................

REFERENCES..................................................................................................................................31

LIST OF FIGURES

Fig.1 Use Case Diagram......................................................................................................................8


Fig.2 ER diagram..............................................................................................................................13
Fig.3 Level 0 DFD..............................................................................................................................16
Fig.4 Level 1 DFD..............................................................................................................................16
Fig.5 Level 2 DFD..............................................................................................................................17

LIST OF TABLES

Table 1: Gantt chart.........................................................................................................................12


Table 2: User Application Testing....................................................................................................22
Table 3: Admin Application Testing.................................................................................................23
Table 4: System Testing.....................................................................................................................25

5
CHAPTER 1: INTRODUCTION
1.1 Project Introduction

This project aims to develop a comprehensive hotel booking website for “ The star hotel ”
that offers a seamless and user-friendly experience for guests and admin. The website will
serve as a digital gateway for potential customers to explore and book rooms, as well as a
robust platform for managing bookings and user details.

Guests will be able to browse through a selection of rooms, each with detailed descriptions,
images, and amenities. The guests can book the rooms with and without login in the website.
Those who are logged in don’t have to enter their credentials as it will be retrieved from the
database. In addition the website will also contain a field for subscribing to the newsletter
field which will pass the email to the admin which will be further used to send personalized
news and promotions by the admin manually.

Administrators will have the ability to update room details, change website elements, and
ensure that the online content reflects the latest offerings of the hotel. The admin panel will
also provide tools to review booking records and manage user details. The admin can add,
edit the rooms details that will be reflected in the main page. And the admin can also manage
the booked services meaning they can approve and reject the bookings.

6
1.2 Objectives

 To create an engaging digital presence for The Star Hotel by developing a visually
appealing and user-friendly website.
 To streamline the room booking process by making reservations easily using their
credentials.
 To enhance user experience with a responsive design .
 To develop a robust admin panel that enables hotel staff to efficiently manage
website content, including room details and availability, as well as monitor and
manage user bookings and information.
 To support efficient hotel operations .
 To enable future scalability by designing the website architecture to accommodate
the addition of features such as a payment gateway, user reviews, and integration
with external booking platforms.

7
1.3 Problem statement

The inspiration for this project arose from observing the websites of various companies and
recognizing that many hotels and guesthouses lack a proper management system in most
areas. To address these challenges, the decision was made to develop a hotel reservation and
booking website. This platform aims to assist users in making online reservations while
helping businesses maintain organized records of their customers and transactions effectively.

Traditional methods of manually recording information in journals are not only inefficient
but also raise concerns about security and accuracy. Additionally, establishing an online
presence can significantly enhance a company's ability to interact with its customers.

Once fully developed and integrated, this project will be ideally suited to help small
businesses manage their operations more efficiently and effectively.

8
1.4 Scope

1.4.1 Website Development:


o Develop a fully functional hotel booking website for The Star Hotel that

includes a user-friendly interface for potential guests to view room options,


hotel amenities, and company information.

o Implement responsive design to ensure the website is accessible and looks


appealing on various devices, including desktops, tablets, and smartphones.

1.4.2 Room Viewing and Booking:


o Allow users to browse available rooms with detailed descriptions, images, and

amenities listed.

o Enable a booking system where users can select rooms and make reservations
using their login credentials.

o Provide a user registration and authentication system to secure the booking


process.

1.4.3 Admin Panel:


o Develop an admin panel for hotel staff to manage website content, including

updating room information, managing bookings, and accessing user details.

o Provide tools within the admin panel to monitor and manage guest bookings
and track occupancy rates.

1.4.4 Content Management:


o Include features for administrators to easily update content on the website,

such as room descriptions, pricing, and availability.

o Ensure that all updates made via the admin panel are reflected in real-time on
the user-facing website.

9
1.4.5 Data Security:
o Implement security measures to protect user data, including encrypted storage

of credentials and secure handling of booking information.

o Ensure compliance with data protection regulations to maintain user trust and
data privacy.

1.5 Limitations

The project, while designed to provide an efficient and user-friendly hotel booking platform,
comes with certain limitations in its initial version. These limitations primarily revolve
around the absence of advanced functionalities and features that could enhance the user
experience and operational efficiency.

1. Absence of Payment Gateway:

o The initial version of the website will not include an integrated payment
gateway, which means users will not be able to complete financial transactions
or pay for their bookings directly through the website.

2. Limited Advanced Features:

o Features such as user reviews, loyalty programs, or third-party service


integrations (e.g., car rentals, travel packages) are not included in the initial
project scope but may be considered for future enhancements.

3. Scalability:

o While the website is designed with future scalability in mind, certain


advanced functionalities, such as multi-language support or integration with
global distribution systems (GDS) for wider booking reach, are not part of the
current project.

10
4. Booking Confirmation Process:

o Without a payment gateway, the booking confirmation process might require


additional manual verification by the hotel staff, which could result in delayed
confirmations.

5. User Experience Dependence:

o The user experience may be impacted by the absence of certain conveniences


like instant booking confirmation via payment, which is a common
expectation in modern online booking systems.

11
CHAPTER 2: REQUIREMENT ANALYSIS

2.1 Finding requirement

The functional requirements define the core capabilities and features that the hotel booking
system must provide to meet the needs of users and administrators. These requirements
ensure that the system facilitates seamless user interactions, supports room booking and
management processes, and integrates essential functionalities such as payment processing
and administrative controls. Each requirement is designed to enhance the overall user
experience while maintaining efficiency, reliability, and scalability in daily operations. The
following are the detailed functional requirements for the system.

2.1.1 Functional Requirement

1. User Registration and Login

o The system will allow users to create an account by registering with a


username, email, and password. Users will be able to log in using their
credentials. Additionally, there will be a password reset functionality available
for users who forget their passwords.

2. Room Browsing and Details

o Users will be able to browse through a list of available rooms on the website.
Each room will have a detailed page displaying information such as images,
descriptions, room types, and pricing.

3. Room Booking

o The system will enable users to select a room and specify the start and end
dates for their stay. Before confirming a booking, the system will check room
availability to prevent double booking. Once a room is selected, users will
provide their personal details (name, email, phone number) to complete the

12
booking process. After successful booking, the system will store the booking
details in the database and display a confirmation message to the user.

4. Booking Management

o Users will have the ability to view their booking history. They will also have
the option to cancel a booking before the start date if needed. For
administrators, the system will provide a dashboard to view all bookings,
along with their statuses.

5. Payment Gateway Integration

o After booking a room, users will be redirected to the eSewa payment gateway
for payment processing. The system will update the booking status to
"Approved" upon successful payment. Administrators will also have the
capability to view payment statuses for each booking through the admin panel.

6. Admin Panel

o The system will include an admin panel that allows administrators to log in
and manage various aspects of the website. This includes the ability to add,
update, and delete room details. Administrators will also be able to manage
user information and bookings, as well as view payment details and booking
statuses.

2.1.2 Non-Functional Requirements

1. Performance

o The system will be designed to respond to user actions within 3 seconds to


ensure a smooth user experience. Additionally, it will be able to handle up to
100 concurrent users without experiencing significant performance
degradation.

13
2. Security

o To protect user data, the system will utilize HTTPS to encrypt all data
transmitted between the client and server. User passwords will be stored using
a strong hashing algorithm. The system will also implement input validation
to prevent security vulnerabilities such as SQL injection and cross-site
scripting (XSS) attacks.

3. Usability

o The website will be user-friendly, with an intuitive and consistent interface


across all pages. Clear and helpful error messages will be provided to guide
users through any issues they may encounter while using the site.

4. Reliability

o The system will be designed for high reliability, with an availability target of
99.9% uptime, excluding scheduled maintenance periods. Additionally, the
system will ensure that booking data is securely saved and not lost, even in the
event of unexpected failures.

5. Scalability

o The system will be scalable to accommodate an increase in user traffic and


data as the business grows. It will be built in a way that allows new features to
be added easily without requiring major changes to existing code.

6. Compatibility

o The website will be compatible with all major web browsers, including
Chrome, Firefox, Safari, and Edge. It will also be designed to be responsive,
providing a seamless experience across both desktop and mobile devices.

14
7. Maintainability

o The system’s codebase will adhere to industry best practices to ensure


readability and ease of maintenance. Automated tests will be included to
verify the correctness of key functionalities, making it easier to identify and
fix issues.

8. Legal and Regulatory Compliance

o The system will comply with relevant data protection regulations, such as the
General Data Protection Regulation (GDPR), to ensure that user data is
handled appropriately. The website will also provide users with clear terms of
service and a privacy policy to outline how their data will be used.

2.1.3 Use case diagram

In Fig. 1, the use case diagram illustrates the primary functionalities of a hotel booking
system, showing interactions between the User (Guest) and Administrator with the system.

User Use Cases:

1. Create Account: Allows users to register on the platform.

2. Login: Required for performing tasks like booking rooms or subscribing to


newsletters (included in several use cases).

3. Viewing Rooms: Enables users to browse available rooms and their details.

4. Booking Rooms: Lets users book rooms after checking availability.

5. Subscribe Newsletter: Allows users to sign up for promotional updates.

6. Gallery: Provides users access to view hotel images.

Admin Use Cases:

15
1. Add/Update Rooms: Administrators can add new rooms or modify existing details.

2. Manage Booking: Admins oversee user bookings, including confirmations and


cancellations.

3. Update Website Elements: Enables updating content and maintaining the site's
functionality.

4. Update Gallery: Allows admins to manage hotel images.

The diagram uses "include" relationships to show dependencies, such as requiring login for
secure access to certain functionalities. It provides a concise representation of the system's
core features for both users and administrators.

16
Fig.1 Use Case Diagram

17
2.2 Feasibility Analysis

The goal of a feasibility analysis is to establish whether or not a project is technically, legally,
and financially feasible before moving any further, which helps in identifying any potential
risks and problems early on.

2.2.1 Technical Feasibility for Hotel Booking Website:

1. Technology Stack:

o Frontend: The website will use standard web technologies such as HTML,
CSS, JavaScript, and potentially frameworks like Bootstrap or React for
responsive design.

o Backend: Laravel (PHP framework) will handle business logic, user


authentication, and room management. Laravel provides features such as
routing, database interaction, and security.

o Database: MySQL will store user data, booking details, room availability, etc.
Laravel’s Eloquent ORM simplifies database operations.

2. Skills and Expertise:

o The project requires knowledge of web development, including Laravel, PHP,


MySQL.

o If additional team members are proficient in these technologies, the project


should be technically feasible.

3. Scalability:

o Laravel’s architecture supports scalability through database optimizations,


caching mechanisms, and distributed systems if needed.

o The system can be deployed on cloud platforms like AWS or DigitalOcean for
better scalability and performance.

18
2.2.2 Operational Feasibility for Hotel Booking Website:

1. Ease of Use:

o The website’s user interface will be designed to be simple and intuitive,


allowing both registered users and admins to interact with the system without
requiring technical expertise.

o Guests will be able to browse rooms, check availability, and book easily, while
admins can manage rooms, bookings, and users effectively.

2. User Training:

o Basic training for administrators on managing bookings, rooms, and user


details will be required.

o Guests and registered users will not require special training as the website will
have a user-friendly interface.

3. Support and Maintenance:

o Regular maintenance will be needed to keep the system secure and up-to-date,
especially regarding room availability and user data.

o Monitoring of server performance, security patches, and periodic backups are


essential to ensure smooth operations.

4. Integration with Existing Systems:

o If the hotel uses any third-party systems for room or booking management,
these will need to be integrated into the website’s backend.

o Integration with payment gateways like eSewa may require ongoing


monitoring to ensure secure and reliable transactions.

19
2.2.3 Economic Feasibility for Hotel Booking Website:

1. Development Costs:

The entire project has been developed using open-source software, including Laravel,
MySQL, and free code editors such as Visual Studio Code. Since these tools do not
require licensing fees, the development costs are significantly reduced. However,
hosting the website on a server incurs an ongoing cost, which can range from $5 to
$50 per month. Additionally, registering a domain name typically costs between $10
and $20 per year. While this is a recurring expense, it remains relatively affordable.

2. Operational Costs:

Although the project has been completed, ongoing maintenance will be essential to
manage security updates, perform regular backups, and address potential bug fixes. If
the website is integrated with a payment gateway like eSewa, there may also be
transaction fees associated with processing payments. These fees are typically a small
percentage of each transaction.

3. Revenue Generation:

The website can generate revenue through booking fees or commissions. For
instance, if the hotel charges a booking fee or takes a percentage of the room price as
a service fee, this could directly contribute to revenue.

4. Return on Investment (ROI):

Given that the project has been developed, the initial investment primarily involved
time rather than significant financial resources. As a result, the financial outlay is
relatively low, allowing the project to potentially break even quickly if the website
generates a consistent flow of bookings. Furthermore, profitability can be
significantly increased by adding more features or integrating advanced technologies
in the future.

20
2.3.4 Schedule Feasibility for Hotel Booking Website:

The project was successfully completed within the scheduled period. Adhering to a
well-defined timeline and project plan, we managed to accomplish all the
development milestones on time. This adherence to schedule feasibility ensured that
the project met its deadlines, delivering the intended functionalities and features
within the expected timeframe. The timely completion of the project demonstrates
effective project management and coordination, contributing to the overall success of
the initiative. Following are the gantt chart for our project.

Table 1: Gantt chart

21
CHAPTER 3: SYSTEM DESIGN

3.1 Er Diagram

Fig.2 ER diagram

In fig 2, the Er diagram represents the core components of the hotel booking system for my
project, covering users, rooms, bookings, and admin roles. Here's a detailed breakdown:

22
 User Entity:

This entity represents the guests or customers who will interact with the system.

Attributes include:

ID: A unique identifier for each user.

name: The user's name.

email: Contact information used for communication and account creation.

phone: The user's phone number.

password: The password for user authentication.

role: Defines the user's role in the system (either as a guest or admin).

 Admin Entity:

The Admin entity handles the management aspect of the system. Admins have higher
privileges to manage room listings and monitor bookings.

Attributes include:

ID: Unique identifier for each admin.

name: Admin's name.

email: Admin's contact email.

phone: Admin's phone number.

password: Admin's login password.

role: Admin role to distinguish from regular users.

23
 Rooms Entity:

This entity stores details about the rooms available for booking at the hotel.

Attributes include:

Room_id: A unique identifier for each room.

Room_title: The title or name of the room (e.g., Deluxe Room, Super Deluxe Room).

image: The image of the room to be displayed on the website.

Des: Short for "description," this provides details about the room's features and amenities.

Room_type: The type or category of the room (e.g., single, double, suite).

Price: The cost per night for booking the room.

 Booking Entity:

The Booking entity captures information when a user books a room.

Attributes include:

Booking_id: A unique identifier for each booking.

Room_id: Links to the room that has been booked.

name: The name of the person making the booking.

email: The email address of the customer.

phone: Contact phone number.

status: The current status of the booking (e.g., confirmed, pending, canceled).

start_date: The check-in date for the booking.

end_date: The check-out date for the booking.

24
3.2 Data Flow Diagram(DFD)

Fig.3 Level 0 DFD

Fig.4 Level 1 DFD

25
Fig.5 Level 2 DFD

26
CHAPTER 4: IMPLEMENTATION AND TESTING

4.1 Tools Used

The system has been implemented using the following technologies: MySQL is for creating
database, HTML and CSS for designing and styling the interfaces, Laravel for creating
communication between client and server. Visual Studio Code has been used as the code
editor for the system.

Tools Used

For the E-commerce website, the following technologies have been used:

Frontend: HTML, CSS, JavaScript, PHP

Backend: PHP, Laravel

Database: MySQL

Code Editor: Visual Studio Code

4.2 Implementation Details of Modules

Implementation details of CRUD (Create, Read, Update, Delete) operations typically involve
developing modules for each functionality. Below are the key steps and considerations for
implementing CRUD operations.

1. Login Page

The login form is made using HTML, CSS, and PHP. To log in, users must first register on
the platform. Once registered, they can use this page to enter their credentials and access
their accounts. This ensures that only authenticated users can access personalized features
and secure areas of the site, enhancing security and user management.

27
2. Add Rooms

This add rooms page is created by utilizing HTML, CSS, and PHP, that allows the admin to
add rooms to the inventory. The admin can input various details such as room name,
category, price, description, and upload images. This functionality ensures that the webpage
is continually updated with new rooms, maintaining the site's relevance and appeal to
customers.

3. Edit Room

The edit room page on our website is made using HTML, CSS, and PHP, it creates a form
that allows the admin to edit the details of existing rooms. This functionality is crucial for
managing the rooms enabling the admin to update room information such as price,
description, and availability status. It ensures that the room data remains accurate and up-to-
date, reflecting real-time changes in availability and other attributes.

4. Delete Room

The delete room page can be accessible only by the admin. Using HTML, CSS, and PHP, it
implemented a functionality that allows the admin to remove rooms from the inventory. This
feature is essential for maintaining the quality and accuracy of the room listings by removing
items that are no longer available or relevant. Restricting access to this page to admins
ensures that room deletions are managed securely and appropriately.

4.3 System testing


Testing in Hotel Booking website is an essential aspect of ensuring a seamless and satisfying
user experience. Testing is the process of evaluating a software room or system to ensure that
it meets its requirements and is fit for use. It involves executing the software with the intent
of finding errors, gaps, or other defects.

Test Cases for Unit Testing

Unit testing is a software testing method that focuses on verifying the correctness of
individual units or components of a system. A unit refers to the smallest testable part of an
application, typically a single function, method, or class. The goal of unit testing is to isolate

28
and test these units in isolation to ensure they work as intended and produce the expected
output for a given set of inputs.

4.3.1 User Application Testing

Table 2: User Application Testing


S.N. Test Case Test Test Data Steps Expected Actual Status
Descripti Executed Results Results
ID
on

i) TC-01 User Email: 1)Click on the Registratio The user pass


registr j16162933 registratio n form is can
ation @gmail.co n button. displayed. register
m User is for a
2)Enter valid
successfull new
Password: user
y registered account.
123456 details and
required
info

ii) TC-02 User Email: 1. Click on the Login form The user pass
login j16162933 login is can
@gmail.co button displayed.
login to
m
2. Enter the User is
the
Password: valid login logged in
system
123456
credentials successfull
y.

29
iii TC-03 Rooms Navigate Rooms are The user pass
) browsi the Rooms displayed can
ng and page. with a list view
selecti of available rooms
Browse
on rooms. and

through rooms
Rooms
the details.
details are

Rooms displayed

options.

iv) TC-04 Book Proceed to The user The user pass


rooms book should be can
able to book
place book availabl
a room. e rooms.

4.3.2 Admin Application Testing

Table 3: Admin Application Testing


S.N. Test Test Test Data Steps Expected Actual Status
Description Executed Results Results
Case ID

i) TC- Admin Email: Click on Admin login The pass


01 login bishesh12 the admin form is admin is
@gmail.co displayed able to
login
m
button login to
Password: the
123456 system.

30
Enter the Admin is
valid login logged in

credentials successfully

ii) TC- Rooms 1.Navigate Rooms The pass


02 to the admin
manageme management
Rooms can add,
nt page is
edit, and
manageme displayed
delete
nt section
Rooms
from the

system.

2.Add a New room is


new
added to the
Rooms to
page
the
Rooms
page.

3.Update Rooms details


the details are
of an successfully
existing
updated
Rooms.

4.Remove Room is
a rooms removed from
from the page
menu

31
4.3.3 System Testing

Table 4: System Testing


S.N. Test Test Test Data Steps Executed Expected Actual Status
Case ID Results Results
Description

i) TC- User login Email: User signup User can User is Pass
01 and j16162933 with username, fill form successful
registratio @gmail.co email, and ly Login.
to
n m password, it
signup,
gets saved to
Password:1 fill sign
database, the
23456 in form
user now signs
and sign
in with the
in to
same
dashboar
credential. d.

ii) TC- User Click on Room User can User Pass


02 Room details and book successful
Booking book room rooms. ly books
according to rooms.
user

requirements.

32
CHAPTER 5: CONCLUSION AND LESSION LEARNED

5.1 Conclusion

In conclusion, the objectives for The Star Hotel's digital platform are focused on delivering a
seamless and engaging user experience while enhancing operational efficiency. The website
will provide users with an intuitive interface for browsing and booking rooms, supported by
responsive design for accessibility across devices. The admin panel will empower hotel staff
to manage content, bookings, and user data effectively. Furthermore, the scalable architecture
will enable the integration of advanced features, such as payment gateways and external
platform connections, ensuring the site remains adaptable to future needs and technological
advancements.

5.2 Future Recommendations

In the future, the Hotel booking system should aim to provide a seamless and convenient
experience for customers. Here are some recommendations to enhance the system:

 Adding Payment Gateway


 Adding user review system
 Personalization and customization
 Booking Cancellation

33
REFERENCES

 OpenAI. (2024). ChatGPT. OpenAI. Retrieved from https://openai.com/chatgpt


 JGraph Ltd. (2024). Draw.io. JGraph Ltd. Retrieved from https://www.draw.io/
 YouTube. (2024). YouTube. YouTube. Retrieved from https://www.youtube.com/
 GitHub. (2024). GitHub Repository. GitHub. Retrieved from https://github.com/
 Dwarika's Hotel. (n.d.). Home. Dwarika's Hotel. Retrieved from
https://www.dwarikas.com/home/

34

You might also like