CHAPTER 1:INTRODUCTION

This application is specially developed to help hotel staff. The project Hotel Management
manages and maintains the records of customers and room in the hotel. The rooms have
different categories such as Deluxe, Semi-Deluxe etc., So their charges and records will be
maintained accordingly.

This software has been made in a user friendly interface, so that anyone can add, delete the
entries of customers and handle all the transactions easily. As a security we have provided
Admin & user level authentication for different modules such as set-up-user etc., also the
user name and password gets stored in the database in encrypted format more dealing
with the security. Customer can either make booking in advance, or he can directly Check-
In. For the convenience of Administration, we have provided facility to generate report of
transactions made in terms of check-in & check-out, bookings by day or specified time
span.

1.1 Features of Project

 HOTEL’S ROOM INFORMATION: It provides User to easily search room’s availability,
category & easy updating of the room’s records. The room numbers and cost per stay
can be changed. Room’s category such as deluxe, semi-deluxe can be edited and
accordingly floor can be set.

 REPORT GENERATION: This feature help’s in easy maintenance of record of

customers check-in, check-out & booking details. The reports can be generated day
wise or specified time span wise.

 PASSWORD PROTECTED: This feature provides privacy to the application. The user
name and password can’t be identified by anybody even if somebody checks it in the
database. As we are encrypting user name & passwords and storing them in the same
format.

 DIFFERENT LOGIN LEVELS: This feature provides different levels of Authentication.

ADMINISTRATOR: Administrator can add and delete rooms, he can add new user, he
can decide the price of the room.
USER: User can do everything except the rights that the Administrator has.

1
1.2OBJECTIVES
The main objective of the entire activity is to automate the process of day to day activities
of Hotel like:
 Room activities,
 Admission of a New Customer,
 Assign a room according to customer’s demand,
 Checkout of a computer and releasing the room
 Finally compute the bill etc.
 Advance bookings.
 Cancellation

This project have some more features:

 No data duplication
 No Paper Work Required
 Time Efficient
 Cost Efficient
 Automatic data validation
 User friendly environment
 Data security and reliability
 Fast data insertion & retrieval
 Easy performance check

1.3Significance of Study
A hotel management system has become an essential need for every business people to
operate.  It holds so many crucial functions to ensure that the hotel management runs
smoothly. The director, manager and other external parties can collaborate easily through
a centralized platform.

2
CHAPTER 2: REQUIREMENT ANALYSIS FEASIBILITY STUDY

2.1 Requirement analysis

Functional Requirements:
Requirement analysis is a software engineering technique that is composed of the various
tasks that determine the needs or conditions that are to be met for a new or altered
product, taking into consideration the possible conflicting requirements of the various
users. Functional requirements are those requirements that are used to illustrate the
internal working nature of the system, the description of the system, and explanation of
each subsystem. It consists of what task the system should perform, the processes involved,
which data should the system holds and the interfaces with the user.

Non-Functional Requirement
It describes aspects of the system that are concerned with how the system provides the
functional requirements. They are:

a. Security: The subsystem should provide a high level of security and integrity of the data
held by the system, only authorized personnel of the company can gain access to the
company’s secured page on the system; and only users with valid password and username
can login to view user’s page.

b. Performance and Response time: The system should have high performance rate
when executing user’s input and should be able to provide feedback or response within
a short time span usually 50 seconds for highly complicated task and 20 to 25 seconds
for less complicated task.

c. Error handling: Error should be considerably minimized and an appropriate error

message that guides the user to recover from an error should be provided. Validation of
user’s input is highly essential. Also the standard time taken to recover from an error
should be 15 to 20 seconds.

d. Availability: This system should always be available for access at 24 hours, 7 days a
week. Also in the occurrence of any major system malfunctioning, the system should be
available in 1 to 2 working days, so that the business process is not severely affected.

3
 e. Ease of use: Considered the level of knowledge possessed by the users of this system,
a simple but quality user interface should be developed to make it easy to understand
and required less training.

2.2 FEASIBILITY STUDY

A feasibility study is carried out to select the best system that must satisfy requirements
and its working ability in an organization.

1. TECHANICL FEASIBILITY:
The technical aspect of feasibility is largely concerned with answering the question of who,
why, where, what and how much in the contact of the existing system and the proposed
system. These questions are asked to the user of the system. An investigation of present
procedure is needed in order to identify the volumes, trends and frequencies that will
specify the affect of the design of any computer based system. In our project all these points
are handled. Based on this we have designed the input screens, table showing list of input
fields with different possibilities of validation and their acceptability to the user gauged
and correction is done whenever it is necessary. Technical feasibility study covers the
technical aspects as far as the automation is concerned.

2. ECONOMIC FEASIBILITY:
During the analysis of economic feasibility, the financial aspects of project is taken into
consideration. As this wizard helps in the faster development of the applications, the time
factor is reduced prominently , thus saving cost. As today’s world requires “Go Green”,
means avoiding unnecessary use of paper, keeping this in mind we tried to make the things
automatically , reducing the paperwork( reducing the skilled people to do the data entry
part) reducing production hours. What we need is person from basic computer
background ,that’s it!

3. OPERATIONAL FEASIBILITY:
Operational feasibility deals with feasibility of the system in operational manner. This
system has been found to very simple & easy to use because it is user friendly. The
operational feasibility is found to be extremely useful. As the proposed system is in VB.NET,
the look is quite understandable to the user, still we providing an official training for them
to handle the application.

CHAPTER 3: SYSTEM DEVELOPMENT

The third chapter states the methodology used to reach the objectives of theproject. The
framework in which software is designed, developed, and maintained is known as the

4
Software Development Life Cycle (SDLC). It shows the steps, phases, milestones, and
evolution of the software development process. There are many types of models used in
software design and development. Among them are the spiral models, rapid development
model, Evolutionary model, waterfall model, prototyping model, etc.

3.1Softwaredevelopment Methodology
For the project Waterfall development model was followed. In the Waterfall approach,
the whole process of software development is divided into separate phases. In this
model, typically, the outcome of one phase acts as the input for the next phase
sequentially.

Fig 3.1: Waterfall Model

3.2 Project Management Strategy and Tools

3.2.1 Project Management Strategy

5
Strategy is the plan of action designed to achieve the overall aim. Since strategy is essential
for creating the vision of entire project and develop the project successfully, we have also
taken proper strategies as mentioned:
We have properly collected the requirements of the project
We have divided the team and tasks according to our strength and ability
We have prepared a timeline for managing time schedule
We do have regular meetings with our team members and regularly consult with our
mentor
We have been working according to our priority list to complete the most important
tasks first.

3.2.2 Project Management Tools

GitHub: It offers all of the distributed version control and source code management.
GitHub Desktop was a common platform for working on the project through different
places by the team members

Lucid Chart: It is the tool used for designing of:

 Flowchart
 Data flow diagram
 ER diagram
 Use Case diagram

MS project: It was used for creating Gantt chart.

3.3 System Design

System Design is the process of defining the components, modules, interface and data for a
system to satisfy specified requirements. Different approaches were used for the system
design purposes which are described below.

3.3.1 DATA FLOW DIAGRAM (DFD)

Data Flow diagram is the process of visualizing or representing the flow of information
within a system. DFD graphically represents the functions, or processes, which capture,
manipulate, store, and distribute data between a system and its environment and between
components of a system.

Symbols in DFD:

6
- External Entity
An external entity can represent a system or subsystem. It is where certain data
comes from or goes to

- Process
A process is a function where the manipulation and transformation of data take place. A
process can be decomposed to a finer level of details, for representing how data is being
processed within the process.

- Data Store
A data store represents the storage of persistent data required and/or produced by the
process.

- Data Flow
A data flow represents the flow of information direction represented by an arrowhead that
shows at the end of the connector.

Types of DFD
Data Flow Diagrams are either Logical or Physical.
● Logical DFD - This type of DFD concentrates on the system process, and flow of data
in the system. For example in a Banking software system, how data is moved
between different entities.

● Physical DFD - This type of DFD shows how the data flow is actually implemented
in the system. It is more specific and close to the implementation

7
Levels of DFD
a. Level - 0 diagram:
It is also known as context diagrams, which are the most basic data flow diagrams. They
provide a broad view but offer little detail. Level 0 data flow diagrams show a single
process with its relationship to external entities.

b. Level - 1 diagram:
They have more details then the context diagram. In 1-level DFD, the context diagram is
decomposed into multiple processes. In this level, we highlight the main functions of the
system and break down the high-level process of 0-level DFD into sub-processes.

c. Level - 2 diagram:
In this level you go one step deeper into parts of level 1 DFD or simply break processes
down into more detailed sub-processes. You will reach in depth of system functioning. It
can be used to plan or record the specific or necessary detail about the system’s
functioning. In theory, DFDs could go beyond level 3, but they rarely do.

Basic rules that apply to all DFDs:

- No internal logic should be shown like loops, if-else, this is not a flow chart
- In order to keep the diagram uncluttered, you can repeat data stores and external
entities.
- No process can have only output data flows (a miracle).
- No process can have only input data flows (black hole).
- Data cannot be moved directly from one store to another without a process.
- Data cannot move directly from an external entity to a data store without a process.
- Data stores can’t be sink (only input data flows) or source (only output data flows) in
level 1 DFD

8
Fig 3.3.1: Level 0 DFD

9
Fig 3.3.1: Level 1 DFD

10
Fig 3.3.1: Level 2 DFD

11
3.3.2 USE CASE DIAGRAM
A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases.

Use cases are a set of actions, services, and functions that the system needs to perform .The
purpose of a use case diagram in UML is to demonstrate the different ways that a user
might interact with a system. Create a professional diagram for nearly any use case using
our.

In the Unified Modeling Language (UML), a use case diagram can summarize the details of
your system's users (also known as actors) and their interactions with the system. To build
one, you'll use a set of specialized symbols and connectors. An effective use case diagram
can help your team discuss and represent:
 Scenarios in which your system or application interacts with people, organizations,
or external systems
 Goals that your system or application helps those entities (known as actors)
achieveThe scope of your system
 The common components of use case diagram includes:

Actors: The users that interact with a system. An actor can be a person, an
organization, or an outside system that interacts with your application or system. They
must be external objects that produce or consume data.

System: A specific sequence of actions and interactions between actors and the
system. A system may also be referred to as a scenario.

Goals: The end result of most use cases. A successful diagram should describe the
activities and variants used to reach the goal.

12
Fig 3.3.2: Use Case Diagram for admin

13
Fig 3.3.2: Use Case Diagram for user

14
3.3.4 SEQUENCEDIAGRAM
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 term event diagrams or
event scenarios to refer to a sequence diagram. sequence diagram describe how and in
what order the object in a system function .these diagram are widely used by businessman
and software developers to document and understand requirements for new or existing
system. It shows interaction of object arranged in time sequence. Sequence diagrams are
typically associated with use case realizations in the logical view of the system under
develop.

15
Fig 3.3.3: sequence diagram for hotel management system

16
Fig 3.3.3: Activity diagram for hotel management system

17
CHAPTER 4: IMPLEMENTATION AND TESTING
4.1 Implementation
System implementation is the process of building properly working systems, testing it and
installing it replacing the old system. In addition, system implementation also includes
preparing the system and user documentation, making the users able to use the system
properly as well as provide continuous support. The basic steps included in system
implementation process are coding, testing, installation, documentation and training. In
this phase the specifications of the project is converted into a working system.
The coding started right after proper analysis of the requirements and theoretical design of
the system. Proper documentation work has been done along with the system development
till the implementation of the system.

4.2 Testing
4.2.1 Unit Testing
Unit test is the smallest testable part of an application like functions, classes, procedures,
interfaces. Unit testing is a method by which individual units of source code are tested to
determine if they are fit for use.
During the coding phase each function was tested to check whether it works properly or
not. Different errors found during unit testing were debugged. Particularly; the user
registration process was tested sending the registration details. If the registration details
are valid the users are registered and their details are inserted into database. Another
testing module was the login process. If the user’s login details are valid then they can login
into to the system. In this way each function, module was tested individually.

4.2.2 System Testing

System testing is done after integration testing in order to ensure that the whole system
functions properly. After the integration testing, the entire system working process was

18
checked. The output was as per the system specifications and hence the system was found
to work properly.

CHAPTER 5: CONCLUSION AND REFERENCES

5.1 CONCLUSION
Hotel Management System can be a crucial factor that can be of great impact in the
economic process in developing countries. With the help of resources and management we
can provide good facility to the people and the visitors . We can attract many visitors with
the facility, service provided to the visitors. Centralized data can be useful for the access of
the information remotely whenever necessary. Security can be maintained by means of
proper authentication and authorization. The software should be user friendly with easy
navigation and promote conservation of environment by removing use of paper.

5.2 REFERENCES
https://creately.com/diagram/example/ikm0vh8e1/hotel-management-system-2-level-1-
[classic]

https://www.scribd.com/doc/141651329/Hotel-Management-System

https://www.academia.edu/36302522/
A_DESIGN_AND_IMPLEMENTATION_OF_ONLINE_HOTEL_MANAGEMENT_SYS
TEM_CASE_STUDY_

19