TRIBHUVAN UNIVERSITY

INSTITUTE OF SCIENCE AND TECHNOLOGY

BIRENDRA MULTIPLE CAMPUS

A PROJECT REPORT ON

“Hotel Booking System”

Submitted in Partial Fulfillment of the Requirements for the:

Bachelors of Science in Computer Science and Information Technology (B.Sc. C.S.I.T)

Submitted by
Asna Bista 56/076(24853/076)
Bibisha Neupane52/076(24859/076)
Malati Chand 75/076 (24869/076)

Submitted To:
Birendra Multiple Campus
Department of computer science and information Technology
Bharatpur-10, chitwan
 SUPERVISOR RECOMMENDATION

I hereby recommend that this project prepared under my supervision by Asna Bista,
Bibisha Neupane, and Malati Chand entitled “Hotel Booking System” in partial
fulfillment of the requirements for the degree of Bachelor of Science in Computer
Science and Information Technology is recommended for the final evaluation.

……………………..

Er. Binod Sharma

HOD, Department of Bsc.CSIT

Birendra Multple Campus

Bharatpur-10, chitwan

1
 APPROVAL LETTER

This is to certify that this project prepared by Asna Bista (24853/076), Bibisha Neupane
(24859/076) and Malati Chand (24869/076) entitled “Hotel Booking System” in partial
fulfillment of the requirement for the Degree of Bachelor in Computer Science and Information
Technology has been well studied. In our opinion, it is satisfactory in the scope and quality
as a project for the required degree.

Signature of the Project Supervisor Signature of the HOD/Coordinator

…………………….. …………………..

Mr. Binod Sharma Mr. Binod Sharma

HOD, Department of CSIT HOD, Department of CSIT

Birendra Multiple Campus Birendra Multiple Campus

Signature of External Examiner Signature of Internal Examiner

……………………… …………………

2
 ACKNOWLEDGEMENT

I’d like to acknowledge the support and contributions of many people, institutions, and
well-wishers without whom this project wouldn’t have been successfully unabridged.
First and foremost, I’d like to express profound gratitude and sincere respect towards
project coordinator and supervisor Mr. Binod Sharma for his patient guidance,
enthusiastic encouragement, and useful critiques from the stage of proposal
development to project development and throughout the report writing until it’s
completion.

I am equally indebted to all family members and friends for sharing their knowledge,
ideas and opinions for project completion which kept me motivated and provided
lifelong inspiration.

I’d also like to acknowledge and extend gratitude to everyone for his/her support and
encouragement for this project.

3
 ABSTRACT

The report includes all the activities performed during development of the Project on
the topic ‘Hotel Booking System’. With advancement in the IT industry and rapid
growth in the usage of internet various works that seems to be impossible some years
before now are straightforward. However, along with the improvement on those things
there are many challenges too. The system “Hotel Booking System” is a web-based
system developed for hotels. This system is developed with the main aim of facilitating
proper administration of hotel activities. The owner can create or remove admins for
the system. Admin can manage the data related to price, room and bookings. In
addition, admin can also manage hotel rooms, booking history, users, and availability.
This system also has the facility to manage customers evaluate the performance of hotel
on monthly and yearly basis. Thus, this system is expected to assist Hotel administrator
in its best ability to manage all facilities of hotel with simplicity, efficiency, and ease.

4
 TABLE OF CONTENT

SUPERVISOR RECOMMENDATION..................................................................................................I
APPROVAL LETTER..............................................................................................................................II
ACKNOWLEDGEMENT.......................................................................................................................III
ABSTRACT..............................................................................................................................................IV
LIST OF ABBREVIATIONS...................................................................................................................1
LIST OF FIGURES...................................................................................................................................2
LIST OF TABLE.......................................................................................................................................3
CHAPTER 1: INTRODUCTION.............................................................................................................4
1.1 Introduction...............................................................................................................................4
1.2 Problem Statements...................................................................................................................4
1.3 Objectives.......................................................................................................................................5
1.4 Scope and Limitation.....................................................................................................................5
1.5 Development Methodology............................................................................................................6
1.6 Report Organization............................................................................................................................7
CHAPTER 2: Background study and Literature Review......................................................................8
2.1 Background Study...............................................................................................................................8
2.2. Literature Review...............................................................................................................................9
CHAPTER 3: SYSTEM ANALYSIS.....................................................................................................10
3.1 System Analysis.................................................................................................................................10
3.1.1 Requirement Analysis....................................................................................................................10
a. Functional Requirement.....................................................................................................................10
b. Non-Functional Requirement.............................................................................................................11
3.1.2. Feasibility Analysis........................................................................................................................12
3.1.3 Analysis...........................................................................................................................................13
3.1.3.1 Data Modeling using ER-diagram..............................................................................................13
3.1.3.2 Process Modelling using DFD.....................................................................................................14
CHAPTER 4: SYSTEM DESIGN..........................................................................................................16
4.1. Design................................................................................................................................................16
4.1.1 Conceptual Model...........................................................................................................................16
4.4.2 Database Design : Transformation of ER to relations and normalization.................................17
4.4.3 Forms and Report Design..............................................................................................................18
4.4.4 Interface and Dialogue Design.......................................................................................................19
Chapter 5: Implementation and Testing................................................................................................20
5.1 Implementation..................................................................................................................................20
5.1.1. Tools used.......................................................................................................................................20
5.1.2. Implementation Details of modules..............................................................................................21
Algorithm.................................................................................................................................................21
5.2 Testing..................................................................................................................................................1
5.2.1 Test Cases for Unit Testing..............................................................................................................1
5.2.2. Test Cases for System Testing........................................................................................................2
5.2.2 Test Case for Login functionality....................................................................................................2
5.2.3 Test Case for Add New Room functionality...................................................................................5
2.5.3 Test Case for View record history functionality.............................................................................8
5.3. Result Analysis..................................................................................................................................12
Chapter 6: Conclusion and Future Recommendation..........................................................................13
6.1 Conclusion..........................................................................................................................................13
6.2 Future Recommendation...................................................................................................................14
REFERENCES........................................................................................................................................15

LIST OF ABBREVIATIONS

ADMIN Administration

APP Application

BSC.CSIT Bachelors of computer science and Information Management

CMD Command

CSS Cascading Style Sheets

DB Database
ER Entity Relationship

HTML Hypertext Markup Language

HBS Hotel Booking System

JS JavaScript

TDH The Deluxe Hotel

TU Tribhuvan University

UML Unified Modeling Language

LIST OF FIGURES

Fig:1.4.1 Project Framework……………………………………………………………….5

Fig:1.5.1 Gantt Chart……………………………………………………………………….6
Fig:3.1.1 Case diagram of functional requirements of hotel booking system…………….10
Fig:3.1.3.1: ER-Diagram of Hotel Booking System………………………………………13
Fig: 3.1.3.2.1: Hotel Room Booking using DFD Level 0…………………………………14
Fig:3.1.3.2.2: Hotel Room Booking using DFD Level -1………………..………………..15
Fig:3.1.3.2.3: Hotel Room Booking Using DFD Level-2………………...……………….15
Fig:4.1.1 conceptual model of HBS………………………………………………………16
Fig:4.4.2: ER to relation of Hotel Booking system……………………………………….17
Fig4.3.3 Forms and Report design………………………………………………………..18
Fig.4.4.4: Interface and Dialogue Design………………………………………………...19
 LIST OF TABLE

Table 5.1.1 Gantt Chart………………………………………………………6

Table: 5.2.2 Test Case for Login functionality……………………………….22

Table: 5.2.3 Test Case for matches Record Functionality……………………24

 CHAPTER 1: INTRODUCTION

1.1 Introduction

Welcome to The Deluxe Hotel, the booking system designed to revolutionize the way booking
done and managed booking. With user-friendly interface and simple features, The Deluce Hotel
is the perfect solution for booking rooms. It’s innovative system streamlines the organization and
manage the booking, making it easy for hotel staff to track rooms booking and makes booking
process quick and easy.

In The Deluxe Hotel, the importance of maintaining an up-to-date and well-organized rooms
booking options. That's why the system provides detailed reports and analytics, allowing staffs to
gain insights into their system and make informed decisions about future acquisitions. With The
Deluxe Hotel, libraries can improve efficiency, enhance user experience, and ensure that their
booking are always up-to-date and managed properly.

Overall, The Deluxe Hotel is an innovative solution that can help libraries improve their
operations and better serve their patrons. Whether a small hotel or a large organization, The
Deluxe Hotels can help to take booking experiences. It look forward to helping streamline in
booking processes.

1.2 Problem Statements

Hotel of all sizes and types are struggles with managing their hotels information and information
collections of their costumer efficiently, leading to difficulties in tracking data, managing
booking process, and providing a seamless costumer experience. So here are some of the
disadvantages of the old traditional practice:

• Manual processes, which are time-consuming and are prone to errors.

• Limited accessibility, as consumers must visit the hotel to book the rooms.
• Limited customization, as the system is often standardized and inflexible.
1.3 Objectives

To solve the Existing problems in Hotel Booking System. Here, the objectives for this project are
Streamlined Booking Process: The primary objective is to provide a seamless and user-friendly
booking process for guests.

Real-Time Availability: The system should ensure that guests have access to accurate and up-to-
date information about room availability, rates, and amenities.

Automated Reservation Management: The system should automate reservation management

tasks, including booking confirmations, modifications, and cancellations.

1.4 Scope and Limitation

The system should allow guests to browse available rooms, view rates, and make reservations
through various online channels such as the hotel's website or mobile app. Guests should have
access to up-to-date information on room availability, ensuring transparency and accuracy in the
booking process.

Limitations:

i. Dependency on Internet Connectivity: Online booking systems are reliant on internet

connectivity, which can pose challenges in areas with poor or unstable internet connections.

ii. Data Security Concerns: Storing and processing sensitive guest information such as payment
details requires robust security measures to protect against data breaches and cyber attacks.
1.5 Development Methodology

Agile Development Methodology is used project because development is divided into small
iterations is Sprints. This is a better development methodology due to its continuous planning,
testing, integration, risk evaluation and control on the progress of the project and there upon
reduces the chances of project failure. Agile is used to plan quickly, develop quickly, release
quickly and revise quickly. In Agile, a project is c Requirements Gathering: In this phase, we
meticulously identify the system requirements,

Planning: Here, it define the project scope, set clear objectives, and construct a comprehensive
project roadmap. It actively engage with stakeholders to identify requirements and prioritize
tasks, ensuring alignment with our overarching goals.

Designing: The design phase focuses on the creation of prototypes and designs based on the
requirements outlined in the planning phase. This step aims to establish a well-defined vision of
the final product.

Developing: During this phase, we undertake the actual development of the software in iterative
sprints. Team works on one feature at a time, thoroughly testing and integrating it into the
product throughout the development journey.

Testing: Rigorous testing is conducted throughout the development process, not just at the end,
to ensure that the software meets the established requirements and operates as intended.

Deploying: Once development is complete, we deploy the software to our end-users. Team
continues to monitor and maintain the product, making improvements and adjustments as needed
to ensure a seamless guest experience.
 Table 1.5.1: Gantt Chart

1.6 Report Organization

This project consists of five chapters. These chapters are classified to make documentation of the
project more transparent. A brief description about the contents of each chapter is given in the
following paragraphs:

Chapter 1: Introduces project, mentions statement of problem, point out objectives,

development methodology and defines project scope and limitation.

Chapter 2: Provides the reader with an overview of the literature review or study of existing
web sites and background study.

Chapter 3: Displays the requirements elicitation which includes (functional requirements,

nonfunctional requirements). feasibility analysis. System Modelling which includes (structured
approach) like Data flow diagram, Entity Relationship Diagram.System Design which also
includes (structured approach) like architecture design database schema design, interface design,
physical DFD.

Chapter 4: System Design

Chapter 5: Defines implementation and testing.

Chapter 6: Displays conclusion, lesson learnt/outcome and future recommendation.

 CHAPTER 2: Background study and Literature Review

2.1 Background Study

Information systems theory focuses on the study of how information and communication
technologies can be used to support organizational goals and objectives. A hotel booking system
relies heavily on database management theory to efficiently store and retrieve information about
room inventory, guest profiles, reservations, and transactions. Concepts such as data
normalization, indexing, and query optimization are fundamental to ensuring the system's
performance and scalability. In the context of a hotel booking system, revenue management
principles are applied to dynamically adjust room rates based on factors such as demand,
seasonality, competitor. CRM theory emphasizes the importance of capturing and analyzing
guest data to tailor personalized experiences, anticipate customer needs, and foster loyalty
through rewards programs, special offers, and personalized communications. pricing, and
booking patterns. This theory helps hotels maximize revenue by selling the right room to the
right customer at the right price and time. To address these issues and enhance the Booking
System experience for both tourist and local people , the “Hotel Booking System” is proposed.
2.2. Literature Review

A literature review can simply a summarise part of what other scholars knows about the topics
that we are intending to work on. It is always based on secondary source. The primary goal of
literature review is to know how other scholars approached to solve the same problem or may be
something related to that. In this research, literature review was carried out for Hotel Booking
System [1].The results of a hotel booking system can be evaluated based on several key
performance indicators that measure its effectiveness in meeting the objectives of the hotel and
providing a satisfactory experience for guests[2].The percentage of available rooms that are
occupied during a specific period. A high occupancy rate indicates effective booking
management and demand for the hotel's rooms. A metric that measures a hotel's revenue
generated per available room, calculated by dividing total room revenue by the total number of
available rooms [5]. Increasing RevPAR indicates improved revenue performance. The average
rate charged per occupied room in a hotel during a specific period. A higher ADR indicates
higher room rates and potentially higher revenue. The percentage of website or mobile app
visitors who complete a booking compared to the total number of visitors. Increasing the
booking conversion rate indicates improved website usability and booking process efficient. The
percentage of bookings that are canceled by guests before their scheduled arrival date. A low
cancellation rate indicates high guest commitment and reduced revenue loss due to cancellations
[4].

By focusing on the growing demand for adventure tourism and benefits of Booking System.
Businesses can tap into the market’s potential for growth and offer an attractive to Hotel.
 CHAPTER 3: SYSTEM ANALYSIS

3.1 System Analysis

3.1.1 Requirement Analysis

a. Functional Requirement

. The admin/user must login into the website with authorized credentials before using it.

. The admin should be able to manage the Room

. The user should be able to manage their Booking.

. The website must be able to access internet and user data.

. The website must be able to identify the user.

. Website must be able to recognize the Service and update in the database.

. Website must be able to compute the cost and inform user.

Fig:3.1.1 Case diagram of functional requirements of hotel booking system

Hotel Booking System

b. Non-Functional Requirement

Non-functional requirements, the quality attributes of the system. The nonfunctional

requirements of Hotel Booking System are explained in following terms:

. Performance: The proposed website should identify users and equipment smoothly within
feasible time.

. Security: The proposed website must be secure from unethical attacks like unauthorized access
of the website.

. Reliability: The website must be reliable so that admin should able to confirm username and
password of authorize users.

. Maintainability: Website must be maintainable when failure occur.

. Availability: Website must be available whenever required.

3.1.2. Feasibility Analysis

Feasibility Study

i. Technical: For both end users and developers project requires a simple hardware i.e. a
computer or a laptop with normal processing speed and GUI based technology as well as good
internet connection and software includes a visual studio code, Apache server, MySQL
database which can be downloaded from many official respective sites. This project is
completed in the most recent and widely used web development tool i.e. React-js as Front end
and Laravel which is a powerful PHP framework with a average footprint(1.7GB), built for
developers who need a simple and elegant toolkit to create full-featured web application. All
the requirements can be easily available so it is technically feasible.Web development tool:
React and Laravel. Tools used: Visual Studio Code, XAMPP, Apache server, MySQL database
Hardware Requirement: A working computer system.

ii. Operational: For the system to work functionally, basic computer knowledge, website
knowledge and power supply is necessary which is abundant in every organization and also as
It mentioned earlier only few technologies will be used to operate the website and simple
training demonstration of working website will be required for admin so it is operationally
feasible.

iii. Economic: As project needs computers and some open source software which can be easily
available through internet surfing and are free of cost, the implementing cost will be very low
compared to other websites with different hardware requirement systems and which uses
premium software for development. Admin can operate our system with less effort and only
few technologies are required so the cost of manpower is not a necessity that’s why it is
economically feasible.

iv. Schedule: For the project to be completed in time

3.1.3 Analysis

3.1.3.1 Data Modeling using ER-diagram

An entity-relationship of graphical representation that depicts system’s entities like people,
objects or concepts, their attributes and the relationship between those entities. The diagram
below shows ER-diagram of “Hotel Booking System”:

Fig:3.1.3.1: ER-Diagram of Hotel Booking System

3.1.3.2 Process Modelling using DFD

The level of detail of each response is at the level of ‘primary use cases’. Each planned response
may be modelled using DFD notation or as a single use case using use case diagram notation.
Data flow diagramming is a highly effective technique for showing the flow of information
through a system. Data flow diagrams reveal relationships among and between the various
components in a program or system.
Fig 3.1.3.2.1 Process Modeling context level-0 DFD

Fig 3.1.3.2.2Process Modeling Level-1 DFD

Fig 3.1.3.3.3 Process Modeling Level-2 DFD
 CHAPTER 4: SYSTEM DESIGN

4.1. Design

4.1.1 Conceptual Model

It can pictorial representation of system architecture that clarifies the concept of the
system. It is a model that visually describes what the system does and the series of
activities within the system. The diagram below shows the conceptual diagram of “Hotel
Booking System”:

Fig:4.1.1 conceptual model of HBS

4.4.2 Database Design : Transformation of ER to relations and normalization

An entity-relationship diagram of graphical representation that depicts system’s entities like

people, objects or concepts, their attributes and the relationship between those entities. The
diagram below shows ER-diagram of “Hotel Booking System”:

Fig:4.4.2: ER to relation of Hotel Booking system

4.4.3 Forms and Report Design

An online hotel booking form used to track bookings and manage reservations through a hotel’s
website. By using an online booking form instead of phone or email bookings, it can reach a
wider audience, make it easier for customers to book rooms in hotel, and boost the number of
bookings gather.

Fig4.3.3 Forms and Report design

4.4.4 Interface and Dialogue Design

The technique that designers use to create user interfaces for software or electronic devices with
an emphasis on aesthetics or style. Designers strive to produce user-friendly and enjoyable
interfaces. The skill of creating user-friendly, intuitive software . Design an intuitive and easy-to-
navigate interface that guides users through the booking process effortlessly. Use clear labeling,
logical grouping of elements, and consistent navigation patterns to help users find information
and complete tasks quickly.

Fig.4.4.4: Interface and Dialogue Design

 Chapter 5: Implementation and Testing
5.1 Implementation

5.1.1. Tools used

Different tools have been used for preparing this project “Hotel Booking System”. The tools WE
have used are listed below:

a.HTML, CSS and Bootstrap : HTML, CSS and Bootstrap are used for creating the design and
template of projects.

b. JavaScript: JavaScript serves as the primary frontend scripting language utilized in the project.

c. SQL: SQL, or Structured Query Language, is employed as the database management system in
this project. It serves as a powerful language for managing, manipulating, and querying relational
databases.

d. Localhost : Localhost is a database WE have used in our project.

e. Command Prompt : Command Prompt is used to run different commands for execution of the
project.

f. Visual Studio Code : Visual Studio Code is the code editor WE have used to create the system.

g. Draw.io : Draw.io is the diagram software used to draw UML diagrams like: use case diagram,
class diagram, sequence diagram and ER diagram.

h. Microsoft Word :Microsoft word is used for preparing documentation of the project.
5.1.2. Implementation Details of modules

Algorithm

Sorting Algorithm (Used in both View Category and View Product): Both components utilize
JavaScript's built-in .sort() method to sort data arrays alphabetically based on a specific
property. In View Category, the category array is sorted alphabetically based on the name
property using the .sort() method with a comparison function (a, b) => a.name. locale
Compare(b.name). In View Product, the product array is sorted alphabetically based on the name
property using the .sort() method with the same comparison function (a, b) => a. name. locale
Compare (b.name). This comparison function compares the name property of two items and sorts
them in alphabetical order in a case-insensitive manner using locale Compare.

Example:-constsorted=[...category].sort((a,b)=>a.name.localeCompare(b.name));
setSortedCategory(sorted);

Search Algorithm (Used in both ViewCategory and ViewProduct): Both components implement
a basic substring search algorithm using the .filter() method to filter data based on a search
query. In ViewCategory, the sortedCategory array is filtered based on whether the name of each
category includes the lowercase search query. The name and search query are converted to
lowercase for a case-insensitive search. In ViewProduct, the sortedProducts array is filtered
based on whether the name of each product includes the lowercase search query. Again, both the
name and search query are converted to lowercase for a case-insensitive search. These
algorithms enable users to sort data alphabetically and search for specific items by name in a
case-insensitive manner, enhancing the user experience when browsing categories and products.

Example:
constfilteredCategories=sortedCategory.filter((item)=>item.name.toLowerCase().includes(sea
rchQuery) )
Hashing Algorithm (Used to encrypt password): Hashing algorithms, such as MD5, SHA-1, or
SHA-256, are used for data security and integrity, particularly when dealing with sensitive
information like passwords. I have used Hash function, which also known as Bcrypt is a widely
used and secure password hashing algorithm that incorporates a salt (a random value) and
multiple rounds of hashing to protect against brute-force attacks and rainbow table attacks.

Example:'bcrypt'=>
['rounds'=>env('BCRYPT_ROUNDS', 10), ],
'password'=>Hash::make($request->password),

5.2 Testing

Testing in a hotel booking system is crucial to ensure its functionality, reliability, security, and
Usability

5.2.1 Test Cases for Unit Testing

Test Case 1: Validate Room Availability Check-in date, check-out date, room type Assert that
the system correctly identifies available rooms of the specified type for the given dates.

Test Case 2: Calculate Reservation Cost Check-in date, check-out date, room rate, additional
charges (if any) Assert that the system accurately calculates the total cost of the reservation
based on the duration of stay and applicable charges.

Test Case 3: Validate User Input Check-in date, check-out date, number of guests Assert that the
system validates user input to ensure that dates are within valid ranges and the number of guests
is within acceptable limits.

Test Case 4: Process Payment Reservation details, payment method, payment amount Assert that
the system successfully processes the payment and updates the reservation status accordingly.

Test Case 5: Update Room Reservation details (check-in date, check-out date, room number)
Assert that the system correctly updates the availability status of the booked room for the
specified dates.
5.2.2. Test Cases for System Testing

It’s identify the possible errors that may occur in the system. This section consists of test
cases for various functionalities of the system. The purpose of testing is to check how
different functionalities work according to different sets of data and find the errors.

5.2.2 Test Case for Login functionality

Table: 5.2.2 Test Case for Login functionality

Module Name: Login functionality

Test Scenario ID: 1

Description: This test case checks the complete login functionality of the system.

Pre-requisite: User must be registered to the system Database

connection should be established.

Test Case ID a. 1_01

b. 1_02

c. 1_03

Test Case a. Check with empty email and password field.

b. Check with invalid email and password.

c. Check with valid email and password.

Test Steps a. Go to Login page.

Click on submit button.

b. Go to Login page

Enter invalid credentials (email and password).

Click on submit button.

c. Go to Login Page

Enter valid credentials (email and password).

Click on submit button.

Test Data a. User ID: ‘’

 Password: ‘’

b. User ID: abcd

Password: ****

c. User ID: Hotelbookingsystem

Password: *****

Expected Result a. User is shown error message to fill the email and
password fields.

b. User is shown error message “Invalid Credentials” and

redirected to login page.

c. User is successfully logged into the system and

redirected to dashboard.

Actual Result a. As expected

b. As expected

c. As expected

Status(Pass/Fail) a. Pass

b. Pass

c. Pass

a. 1_01
b. 1_02

c. 1_03
5.2.3 Test Case for Add New Room functionality.
Table: 5.2.3 Test Case for matches Record Functionality

Module Name: Add new room Functionality

Test Scenario Id: 2
Description: This test case checks the functionality for match costumer history data.
Pre-requisite: Database connection should be established.
Test Case ID a. 2_01

b. 2_02

Test Case a. Check with empty data.

 Check with valid data
b.

Test Steps a. Go to add room page.

Click on “+New” button to add room popup.
Click on submit button.
b. Go to add room page.
Click on “+New” button to add room popup. Enter
valid data for all fields (Room Type, Number of
room).
Click on submit button.
Test Data a. All fields are empty.

b. Room Type: “Single Bedded”

Number of Room: “3”
Expected Result a. Error message is displayed to enter the field data.
b. New Room record is successfully inserted into
database and redirected to successful message
page with success message.

Actual Result a. As expected

b. As expected

Status(Pass/Fail) a. Pass
b. Pass
a. 2_01

B. 2_02
2.5.3 Test Case for View record history functionality.

Table: 2.5.3 Test Case for Bookings record Functionality

Module Name: Add new room Functionality
Test Scenario Id: 2
Description: This test case checks the functionality for match costumer history data.
Pre-requisite: Database connection should be established.
Test Case ID a. 3_01
b. 3_02
Test Case a. Test with invalid data
b. Test with valid data
Test Steps a. Go to the main page.
Click on “Booking History” button to
get booking history popup.
Enter invalid booking id and time
range.
Click on the submit button.
b. Go to the main page.
Click on “Booking History” button to
get booking history popup.
Enter a valid booking id and time
range.
Click on the submit button.

Test Data a. Booking Id: “121212”

Date Range: “12/03/2024 to
12/21/2024”.
b. Boking Id : “10013”
Date Range: “09/05/2017 to
12/05/2024”

Expected Result a. Show error message while providing

invalid data in specific field.
b. Booking history successfully show
while provide valid data in specific
field.
Actual Result a. As Expected
b. As Expected

Status(Pass/Fail) a. Pass
b. Pass
a. 3_01
b.3_02
5.3. Result Analysis

Occupancy Rate Analyze the occupancy rate to determine the percentage of rooms occupied over
a specific period. Identify trends in occupancy rates to assess demand patterns and optimize
pricing and inventory management strategies. Revenue Performance Evaluate revenue metrics
such as Revenue per Available Room (RevPAR), Average Daily Rate (ADR), and Total
Revenue. Compare revenue performance against targets and benchmarks to assess the system's
contribution to revenue generation. Booking Channel Mix Analyze the distribution of bookings
across different channels, including direct bookings online travel agencies (OTAs), and other
distribution channels. Determine the proportion of revenue generated from each channel and
optimize marketing and distribution strategies accordingly. Conversion Rates Measure
conversion rates for different stages of the booking process, such as website visits to bookings
and booking inquiries to confirmed reservations. Identify factors influencing conversion rates
and implement strategies to improve conversion rates and booking efficiency. Customer
Satisfaction Gather feedback from guests through post-stay surveys, online reviews, and social
media channels.
 Chapter 6: Conclusion and Future Recommendation

6.1 Conclusion

The project ‘Hotel Booking System’ was developed with primary motive to facilitate the owner
of hotel. HBS is designed for people who want to manage activities of hotel in simple, modern,
and efficient way. With rising interest and passion for hospitality, hotels are increasing in
number across the country. This specific project aims to address the challenges in hotel
management. This project involves the development of HBS (Hotel Booking System), designed
to empower hotel owners to efficiently manage various data and activities within their
establishments. The HBS replaces the labor-intensive process of record-keeping with a
streamlined, computerized, and user-friendly system. The system is tailored to meet the specific
needs of hotel owners by transitioning from manual operations to a digitized system, thereby
reducing workloads and enhancing the efficiency of managing data and activities. An admin
using this system can effectively oversee and manage various records such as pricing, guest logs,
reservation details, staff training records, event bookings, employee data, subscription
information, supplier records, customer data, and billing. Furthermore, the system provides the
capability for administrator. This comprehensive view enables a clearer understanding of the
hotel's financial status and operational performance. Hence, the system was completed
overcoming the challenges faced by hotel owners in managing hotel.The system was tested by
both developer and user. Finally, the project was obtained as a system that converts manual
processes into computerized system of recording the information that is simple and efficient.
6.2 Future Recommendation

Although the project HMS has been completed, which overcomes the problems related to hotel
management, there are still some functionalities that can be added for better performance. Some
of them are:

i. Integrate search function.

ii. Use external data sources to provide more comprehensive and personalized book
recommendations based on user desire and interest.
iii. Implement a feature for users to leave rooms reviews and ratings directly on the
platform.
iv. Create a community-driven system.
v. Provide valuable feedback for the hotels to improve their rooms and facility.
 REFERENCES

[1] PHP tutorial. Available at: https://www.w3schools.com/php/ [Accessed: 11 Jan 2024].

[2] The largest selection of hotels, homes, and holiday rentals (no date) Booking.com. Available
at: https://www.booking.com[Accessed: 17 Jan 2024].
[3] MozDevNet MDN Web Docs, MDN Blog RSS. Available
at: https://developer.mozilla.org/ [Accessed: 17 Jan 2024].
[4] “Learn to use Bootstrap,” https://getbootstrap.com/docs/ [accessed feb. 1, 2024].
[5] Deals & discounts for hotel reservations from luxury hotels to budget
accommodations Hotels.com. Available at: https://www.hotels.com/ [Accessed: 12 march 2024]