lOMoARcPSD|38874687

Hotel Managment system project

software engineering (Government College University Faisalabad)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Sun Star (sunstarsuraj806@gmail.com)
 lOMoARcPSD|38874687

PROJECT REPORT
ON
HOTEL MANAGEMENT SYSTEM

Session
2020-24

GUIDED BY:
SUBMITTED BY:
MR.USMAN HABIB
ZEESHAN NAZISH
PROFESSOR
BILAL PERVAIZ ASPIRE COLLEGE
HAMMAD HASSAN GUJAR KHAN
Downloaded by Sun Star (sunstarsuraj806@gmail.com)
 lOMoARcPSD|38874687

Dedication
We would like to dedicate this project to our beloved teacher Mr. Usman Habib
who always helped and guided us not about this project but also about life.
They made us stronger to face the difficulties not in the project but also in
every field of life. We are very thankful to him for sharing their knowledge with
us.

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Acknowledgement
This project is dedicated to our parents for their endless support, love and
encouragement. Without whom none of our success would be possible. They
are source of inspiration for us. They always pray for us and our success. This
project is also dedicated to our all teachers who worked hard for us. This
project is also dedicated to our brothers, sisters, friends and the entire person
who encourage us.

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Table of Contents
Dedication.............................................................................................................................................2
Acknowledgement.................................................................................................................................3
1.1 Introduction of the project..............................................................................................................7
1.2 Objective of project.........................................................................................................................7
1.3 Scope of Project...............................................................................................................................7
1.4 Acronyms and Abbreviations...........................................................................................................7
Requirements........................................................................................................................................8
2.1 Hardware Requirements..............................................................................................................8
2.2 Software Requirements...............................................................................................................8
2.3 Functional Requirements.............................................................................................................8
2.4 Non Functional Requirements.....................................................................................................8
Models...................................................................................................................................................9
3.1 Waterfall Model...........................................................................................................................9
3.1.1 Figure Waterfall model.......................................................................................................10
3.2 Incremental Model....................................................................................................................10
3.2.1 Figure Incremental Model...................................................................................................11
UML.....................................................................................................................................................12
4.1 Use Case Diagram......................................................................................................................12
4.1.1 Figure Use Case Diagram....................................................................................................13
4.2 ER Diagram................................................................................................................................14
4.2.1 Figure ER Diagram...............................................................................................................15
4.3 Activity Diagram.........................................................................................................................16
4.3.1 Figure Activity Diagram.......................................................................................................17
4.4 Class Diagram.............................................................................................................................18
4.4.1 Figure Class Diagram...........................................................................................................18
4.5 State Chart Diagram...................................................................................................................19
4.5.1 Figure State Chart Diagram.................................................................................................20
4.6 Data Flow Diagram.....................................................................................................................21
4.6.1 Data Flow Diagram (Level 0)...............................................................................................22
4.6.1.1 Figure Data Flow Diagram(Level 0)...................................................................22
4.6.2 Data Flow Diagram (Level 1)...............................................................................................23
4.7 Sequence Diagram.....................................................................................................................24

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.7.1 Figure Seqeunce Diagram...................................................................................................25

4.8 Collaboration Diagram...............................................................................................................26
4.8.1 Figure Collaboration Diagram.............................................................................................27
5.1 GUI.................................................................................................................................................28

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

1.1 Introduction of the project

“Hotel Management” (a project for keeping customers record and also
calculate customer bill slip and managers salary).
The name of project is “Hotel Management”. The objective of project is to
computerize the system of the hotel. “Hotel Management” is the project not
only keeps the record of various people like customers, manager etc. But as

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

well as it reduce the extensive paper work in the present system. It makes the
system more versatile and user friendly. It also calculates the proper billing slip
of high level and middle level customers. This project is based on description
about the structure of HOTEL MANAGEMENT SYSTEM. The project contains:
 Keeping the record of all persons like customers, managers etc.
 Maintains proper list of all persons.
 Generating proper bill slip and calculate managers salary.

1.2 Objective of project

The main objective of the project is to manage the detail of Hotel,
Rooms, Services, Payments, and Bookings. It manages all the information about
Hotel, Customers and Bookings. The purpose of the project to build an
application program to reduce the manual work for managing the Hotel,
Rooms, Customers, Services. It tracks all the detail about the Services,
Payment, and Bookings.

1.3 Scope of Project

The software to be developed deals with creating a Hotel Management
System which will automate the major hotel operations such as generating
COD, billing, and keeping track of records of daily transaction. Admin have the
authority to control and modify the database. It will help a person to know the
management of passed year perfectly.

1.4 Acronyms and Abbreviations

H.M.S --> Hotel Management System
SRS --> Software Requirements Specifications
SQL --> Structured Query Language
COD--> Cash on Delivery

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Requirements
2.1 Hardware Requirements
PC
Dual Core – 1.8 GHz processor or better
4GB RAM
Keyboard and Mouse
2.2 Software Requirements
Windows 7, 8, 8.1, 10, or 11

2.3 Functional Requirements

 Make Reservation
 Search Room
 Add Payment
 Issue Bills
 Manage Guest (Add, Update, Delete)
 Manage Room Detail (Add, Update, Delete)
 Manage Staff (Add, Update, Delete)
 Set Rates

2.4 Non Functional Requirements

 Safety Requirements
 Security Requirements
 Performance

Models
The Software developments models are the various processes or
methodologies that are being selected for the developments of the project
depending on the project’s aim and goals. There are many Development life
cycle models that have been developed in order to achieve different required
objectives. Here are some important models:

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

 Waterfall Model
 Incremental Model

3.1 Waterfall Model

The waterfall model was the first process model to be introduced.
It is also referred as linear sequential life cycle model. It was very simple
and easy to understand. In waterfall model, each phase must be
complete before the beginning of next phase. The waterfall model is the
earliest sdlc approach that was used for software development. The
phases in waterfall model are:
1. Requirements
All the possible requirements of the system to be developed
are captured in this phase and documented in a requirements
specification document.
2. System Design
The requirement specification from the first phase are
studied in this phase and system design is prepared. It helps in defining
the overall system architecture.
3. Implementation
This is actual writing of a program. The system is first
developed in small programs called units, which are integrated in next
phase.
4. Integration and Testing
All the units developed in the implementation phase are
integrated into a system after testing of each unit.
5. Deployment
Once the functional and non functional testing is done; the
product is deployed in the customer environment or released into the
market.
6. Maintenance

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

These are some issues which come up in the client

environment. To fix those issues the better version of the software is
released.

3.1.1 Figure Waterfall model

3.2 Incremental Model

Incremental Model is a process of software development where
requirements divided into multiple standalone modules of the software
development cycle. In this model, each module goes through the
requirements, design, implementation and testing phases. Every
subsequent release of the module adds function to the previous release.
The process continues until the complete system achieved. Phases ain
incremental model are as follow:
1. Requirements

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

All the possible requirements of the system to be developed

are captured in this phase and documented in a requirements
specification document. To develop the software under the incremental
model, this phase performs a crucial role.
2. Design & Development:
In this phase of the Incremental model of SDLC, the design
of the system functionality and the development method are finished
with success.
3. Testing:
In the incremental model, the testing phase checks the
performance of each existing function as well as additional functionality.
In the testing phase, the various methods are used to test the behavior
of each task.
4. Implementation:
Implementation phase enables the coding phase of the
development system. It involves the final coding that design in the
designing and development phase and tests the functionality in the
testing phase.

3.2.1 Figure Incremental Model

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

UML
UML (Unified Modelling Language) is a general-purpose, graphical
modelling language in the field of Software Engineering. UML is used to specify,
visualize, construct, and document the artefacts (major elements) of the
software system. It was initially developed by Grady Booch, Ivar Jacobson, and
James Rumbaugh in 1994-95 at rational software, and its further development
was carried out through 1996. In 1997, it got adopted as a standard by the
Object Management Group. The types of UML are:
 Use case diagram
 ER diagram
 Activity Diagram
 Class Diagram
 State Chart Diagram
 Data flow Diagram(Level 0 and Level 1)
 Sequence diagram
 Collaboration diagram
4.1 Use Case Diagram
Use-case diagrams describe the high-level functions and scope of a
system. These diagrams also identify the interactions between the system and
its actors. The use cases and actors in use-case diagrams describe what the
system does and how the actors use it.

The following topics describe model elements in use-case diagrams:

Use cases
A use case describes a function that a system performs to achieve the
user’s goal.

Actors
An actor represents a role of a user that interacts with the system that

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

you are modeling. The user can be a human user, an organization, a

machine, or another external system.

Association
An association is a connection between an actor and a use case.

4.1.1 Figure Use Case Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.2 ER Diagram
An ER diagram is a graphical representation of tables (entities) in a
database and the relationship between them. It was developed by Peter Chen
in 1976. ER diagram uses different symbols to represent three types of
information as follows:
Rectangle
It is used to represent entities. An entity can be a person, place or
anything about which data is collected.

Entity
Diamond

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

It normally used to represent the relationships. The relationship

indicates how the entities are related to each other.

Relationship

Oval
It is used to represent the attributes. The attributes is used to define the
entity. An entity may have many attributes.

Attributes

These Symbols also used in ER Diagram to show the relationship between

entities.

4.2.1 Figure ER Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.3 Activity Diagram

Activity diagram is basically a flowchart to represent the flow from
one activity to another activity. The activity can be described as an operation of
the system.
Basic components of an activity diagram are:
 Action: A step in the activity wherein the users or software perform a
given task. In Lucid chart, actions are symbolized with round-edged
rectangles.

 Decision node: A conditional branch in the flow that is represented by a

diamond. It includes a single input and two or more outputs.

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

 Control flows: Another name for the connectors that show the flow
between steps in the diagram.

 Start node: Symbolizes the beginning of the activity. The start node is
represented by a black circle.

 End node: Represents the final step in the activity. The end node is
represented by an outlined black circle.

4.3.1 Figure Activity Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.4 Class Diagram

Class diagram describes the attributes and operations of a class and also
the constraints imposed on the system. The class diagrams are widely used in
the modelling of object-oriented systems because they are the only UML
diagrams, which can be mapped directly with object-oriented languages.
Class Notation

A class notation consists of three parts:

Class Name
 The name of the class appears in the first partition.
Class Attributes
 Attributes are shown in the second partition.

Class Operations (Methods)

 Operations are shown in the third partition.

4.4.1 Figure Class Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.5 State Chart Diagram

The name of the diagram itself clarifies the purpose of the
diagram and other details. It describes different states of a component in a
system. The states are specific to a component/object of a system. A Statechart
diagram describes a state machine. Basic State Chart Diagram Symbols are:
States

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

States represent situations during the life of an object. You can

easily illustrate a state in SmartDraw by using a rectangle with rounded
corners.

Initial State
A filled circle followed by an arrow represents the object's initial
state.

Final State
An arrow pointing to a filled circle nested inside another circle
represents the object's final state.

Transition
A solid arrow represents the path between different
states of an object.

4.5.1 Figure State Chart Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.6 Data Flow Diagram

Data flow diagrams are used to graphically represent the flow of
data in a business information system. DFD describes the processes that
are involved in a system to transfer data from the input to the file
storage and reports generation.
Symbols used in DFD are:

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

1. External entities are represented by squares as the source or

destination of data.
2. Processes are represented by rectangles with rounded corners.
3. Data Flows are referred to by arrows to denote the physical or
electronic flow of data.
4. Data Stores Different processes can store and can get the data from
the data store. Data store means a simple database table.

4.6.1 Data Flow Diagram (Level 0)

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the
whole system or process being analyzed or modeled. It’s designed to be an
at-a-glance view, showing the system as a single high-level process, with its
relationship to external entities.

4.6.1.1 Figure Data Flow Diagram(Level 0)

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.6.2 Data Flow Diagram (Level 1)

Level 1 DFDs are still a general overview, but they go into more detail
than a context diagram. In a level 1 data flow diagram, the single process
node from the context diagram is broken down into subprocesses. As these
processes are added, the diagram will need additional data flows and data
stores to link them together.

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.6.2.1 Figure Data Flow Diagram (Level 1)

4.7 Sequence Diagram

A sequence diagram simply depicts interaction between
objects in a sequential order i.e. the order in which these interactions take
place. We can also use the terms event diagrams or event scenarios to refer
to a sequence diagram.
A quick overview of the various part of sequence diagram.

Lifeline
A lifeline represents an individual participant in the Interaction .

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Call Message
A message defines a particular communication between Lifelines
of an Interaction.

Return Message
A message defines a particular communication between Lifelines
of an Interaction.

Self Message
A message defines a particular communication between Lifelines
of an Interaction.

4.7.1 Figure Seqeunce Diagram

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

4.8 Collaboration Diagram

The collaboration diagram is used to show the relationship
between the objects in a system. Both the sequence and the collaboration
diagrams represent the same information but differently. Instead of showing
the flow of messages, it depicts the architecture of the object.
Major components of a collaboration diagram are:
Objects-
Objects are shown as rectangles with naming labels inside.

Object

Links-
Links connect objects with actors and are depicted using a solid
line between two elements. Each link is an instance where messages can be
sent.

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Messages-
Messages between objects are shown as a labeled arrow placed
near a link. These messages are communications between objects that convey
information about the activity and can include the sequence number.

4.8.1 Figure Collaboration Diagram

5.1 GUI

Downloaded by Sun Star (sunstarsuraj806@gmail.com)

 lOMoARcPSD|38874687

Downloaded by Sun Star (sunstarsuraj806@gmail.com)