UNIVERSITY OF ADEN

FACULITY OF ENGINEERING
SETION OF INFORMATION TECHNOLOGY

HOTEL RECEPTION SYSTEM

Prepared by: Project Supervisor:

Akram Shawki 217029 Dr. Hashem

Amal Bayonis 217013 Eng. Kamal
Hala Khaled 217031
Aisha Gamal 217016

December 2023
 ACKNOWLOGMENT

First and from the deep of our hearts we thank Allah for giving us the strength to
complete this project, then we thank our project supervisors Dr. Hashem and Eng. Kamal,
for providing all the help for us to complete this project to the fullest. On the other hand,
we thank all the teachers who taught us and gave us valuable information as we benefited
from it well, and we hope that this project is an appreciation of their efforts and patience
with us. We are the students of the Department of Information Technology and
Engineering of the third year.

I
 APROVAL SHEET

Prepared by:

Akram Shawki 217029

Amal Bayonis 217013
Hala Khaled 217031
Aisha Gamal 217016

Project Supervisor: Signature: Date:

Dr. Hashem ………………. \ \2023

Eng. Kamal …………………. \ \2023

II
 ABSTRACT

The hotel system is one of the systems used globally, but some hotels suffer from
overlapping reservations when dealing with Multiple bookings at the same time. It may
occur due to conflicting room reservations and available dates. This leads to simultaneous
booking of the same room and the same date for different customers, and to solve this
problem we thought of a modern solution using a special database to facilitate the process
of organizing reservations.
This project aims at creating on Hotel Management System which can be used by Admin
and Customers.
The total front end was dominated using HTML standards applied with the dynamism of
JAVA server pages. The communicating client was designed using servlet and JSP’s. At
all proper levels high care was taken to check that the system manages the date
consistency with proper business validations. The database connectivity was planned
using the Java Data Base Connectivity , the authorization and authorization was cross
checked at all stages. The user level accessibility has been restricted into two zones the
administrative and the normal user zone.

III
 INDEX OF CONTENTS

Contents
ACKNOWLOGMENT .................................................................................................................. I
APROVAL SHEET ....................................................................................................................... II
ABSTRACT .................................................................................................................................. III
INDEX OF CONTENTS.............................................................................................................. IV
INDEX OF TABELS .................................................................................................................... VI
INDEX OF Figures ...................................................................................................................... VII
CHAPTER 1 .................................................................................................................................. 1
Introduction ................................................................................................................................. 1
1.1 Overview: ................................................................................................................... 2
1.2 Project Objective: ...................................................................................................... 2
1. Save time on admin tasks. ............................................................................................. 2
2. Increase your online visibility. ...................................................................................... 2
3. Manage distribution functions. ...................................................................................... 2
4. Increase bookings. .......................................................................................................... 2
5. Accurate daily reports. ................................................................................................... 2
6. Prevent double bookings and manual errors................................................................. 2
7. Analyze your customer base. ......................................................................................... 2
1.3 Purpose: ......................................................................................................................... 2
1.4 Scope: .............................................................................................................................. 2
1.5 Software Requirement Specification: ................................................................ 3
CHAPTER 2 .................................................................................................................................. 4
System Analysis .......................................................................................................................... 4
2.1 Overview: ......................................................................................................................... 5
2.1.1 SDLC Model: ......................................................................................................................... 5
2.2 Purpose of system analysis: ............................................................................................ 5
2.3 Entity Diagram Relations (ERD): .................................................................................. 6
2.4 Flow Chart Diagram: ......................................................................................................... 7
2.5 Use Case Diagram: .......................................................................................................... 8
2.6 Sequence Diagram:.......................................................................................................... 9

IV
CHAPTER 3 ................................................................................................................................ 11
System Design ........................................................................................................................... 11
3.1 Overview: ....................................................................................................................... 12
3.2 Purpose: .......................................................................................................................... 12
3.3 Interfaces:....................................................................................................................... 12
3.3.5 Reservation Interface: ................................................................................................. 16
............................................................................................................................................... 16
...................................................................................................... .‫معرفة‬
ّ ‫خطأ! اإلشارة المرجعية غير‬
1.1.1 Requests Interface: ............................................................................................... 17
............................................................................................................................................... 17
...................................................................................................... .‫معرفة‬
ّ ‫خطأ! اإلشارة المرجعية غير‬
GANTT CHART .................................................................................................................. 18
A Gantt chart is a commonly used graphical depiction of a project schedule. It's a type of
bar chart showing the start and finish dates of a project's elements such as resources,
planning, and dependencies. ................................................................................................. 18
............................................................................................................................................... 18
...................................................................................................... .‫معرفة‬
ّ ‫خطأ! اإلشارة المرجعية غير‬
CONCLUSION..................................................................................................................... 19
REFERENCES ............................................................................................................................ 20

V
 INDEX OF TABELS

TABLE 1 ............................................................................................................................................................. 3
TABLE 2 ............................................................................................................................................................. 3

VI
 INDEX OF Figures

FIGURE 1 ........................................................................................................................................................... 5
FIGURE 2 ........................................................................................................................................................... 6
FIGURE 3 ........................................................................................................................................................... 7
FIGURE 4 ........................................................................................................................................................... 8
FIGURE 5 ........................................................................................................................................................... 9
FIGURE 6 ......................................................................................................................................................... 10
FIGURE 7 ......................................................................................................................................................... 12
FIGURE 8 ......................................................................................................................................................... 13
FIGURE 9 ......................................................................................................................................................... 14
FIGURE 10 ....................................................................................................................................................... 15
FIGURE 11 ....................................................................................................................................................... 16
FIGURE 12 ....................................................................................................................................................... 17
FIGURE 13 ....................................................................................................................................................... 18

VII
CHAPTER 1
Introduction

1
1.1 Overview:
The entire project has been developed keeping in view of the Distributed client server
computing technology in mind. The specification have been normalized up to 3NF to
eliminate all the anomalies that may arise due to the database transactions that are
executed by the actual administration and users. The user interfaces are browser specific
to give distributed accessibility for the overall system. The internal database has been
selected as Oracle 11g.The basic constructs of the tablespaces, clusters and radixes have
been exploited to provide higher consistency and reliability for the data storage. The
oracle 11g was a choice as it provides the constructs of high level reliability and security.
The total front end was dominated using HTML standards applied with the dynamism of
JAVA server pages. The communication client was designed using servlets. At all proper
levels high care was taken to check that the system manages the date consistency with
proper business validations. The database connectivity was planned using the Java
Database Connectivity, the authorization and authorization was cross checked at all
stages. The user level accessibility has been restricted into two zones the administrative
and the normal user zone.

1.2 Project Objective:

1. Save time on admin tasks.
2. Increase your online visibility.
3. Manage distribution functions.
4. Increase bookings.
5. Accurate daily reports.
6. Prevent double bookings and manual errors.
7. Analyze your customer base.

1.3 Purpose:
The main purpose of preparing this document is to give a general idea about facilitating
the hotel reservation process for customers, through online reservations.

1.4 Scope:
This Document plays a vital role in the development life cycle (SDLC) As it describes
the complete requirement of the system. It is meant for use by the developers and will be
the basic during testing phase. Any changes made to the requirements in the future will
have to go through formal change approval process.

2
1.5 Software Requirement Specification:

1.5.1 Hardware Requirements:

Table 1

Number Description

1 PC with 250 GB or more Hard disk.

2 PC with 2 GB RAM.

3 PC with Pentium 1 and Above.

4 Local Networks

1.5.2 Software Requirements:

Table 2

Number Description Type

1 Operating System Windows 2010

2 Language C#

3 Database MySQL

4 IDE Visual Code

5 Browser Google Chrome

3
CHAPTER 2
System Analysis

4
2.1 Overview:
A system analysis is an in-depth evaluation of the processes involved in creating a
product or service. A focus on the people within the system and empathy for those
persons accessing the system can provide information for solving problems or planning
for development or changes in processes. The analysis should result in evidence of
patterns and trends within the organization and consider external factors that may affect
the organization.

2.1.1 SDLC Model:

Software Development life cycle (SDLC) is a spiritual model used in project
management that defines the stages include in an information system development
project, from an initial feasibility study to the maintenance of the completed application.

There are different software development life cycle models specify and design, which are
followed during the software development phase. These models are also called "Software
Development Process Models." Each process model follows a series of phase unique to
its type to ensure success in the step of software development.

The waterfall model: is a classical model used in

system development life cycle to create a system
with a linear and sequential approach. It is termed
as waterfall because the model develops
systematically from one phase to another in a
downward fashion. This model is divided into
different phases and the output of one phase is
used as the input of the next phase. Every phase
has to be completed before the next phase starts

and there is no overlapping of the phases. Figure 1

2.2 Purpose of system analysis:

Collecting information to be analyzed is the main purpose of a system analysis. This may
be used to make decisions, solve problems, become more efficient, or to expand. The
goal would be to have as many people who understand the process to provide reliable
information for set policies and procedures while building in a feedback loop to ensure
ongoing support and operations.

5
2.3 Entity Diagram Relations (ERD):

Figure 2

6
2.4 Flow Chart Diagram:

Figure 3

7
2.5 Use Case Diagram:

Figure 4

8
2.6 Sequence Diagram:
2.6.1 Sequence In Online System:

Figure 5

9
2.6.2 Sequence In Reception System:

Figure 6

10
CHAPTER 3
System Design

11
3.1 Overview:
Systems design is the process of defining elements of a system like modules,
architecture, components and their interfaces and data for a system based on the specified
requirements. It is the process of defining, developing and designing systems which
satisfies the specific needs and requirements of a business or organization.

3.2 Purpose:
The purpose of systems design is to define, organize, and structure the components of the
final solution system that will serve as the blueprint for construction.

3.3 Interfaces:
3.3.1 Login Interface For Reception:

Figure 7

12
3.3.2 Add And Edit Accounts Interface :

Figure 8

13
3.3.3 Room Interface:

Figure 9

14
3.3.4 Customer Interface:

Figure 10

15
3.3.5 Reservation Interface:

Figure 11

16
1.1.1 Requests Interface:

Figure 12

17
 GANTT CHART

A Gantt chart is a commonly used graphical depiction of a project schedule. It's a type of
bar chart showing the start and finish dates of a project's elements such as resources,
planning, and dependencies.

Figure 13

18
 CONCLUSION

In conclusion, hotel management must prioritize customer satisfaction, customer

facilitation, operational efficiency, financial performance, employee satisfaction and
retention, brand image and reputation, innovation and adaptation, environmental
sustainability, safety and security, community engagement, and strategic partnerships to
achieve its goals. Hotels that focus on these goals can create a competitive advantage,
attract more customers, and generate higher revenues while contributing to the local
community and environment.

The cheapest option is not always the best option – and the same goes for the most
expensive choice. There are many inexpensive products that will end up costing you
money if you’re not careful when buying a hotel management software system.

Take the time to do some extensive research before investing in the right system for your
hotel business. Make sure you get feedback from each of your departments and
understand their specific needs before deciding on a solution.

19
 REFERENCES

1. https://www.cerritos.edu/dwhitney/SitePages/CIS201/Lectures/IM-
7ed-Chapter06.pdf
2. https://opus.govst.edu/cgi/viewcontent.cgi?article=1199&context=ca
pstones
3. https://online.visual-paradigm.com/community/share/hotel-
reservation-use-case-diagram-rlsx3mukl

20