MVPS’s

RAJARSHI SHAHU MAHARAJ POLYTECHNIC,

NASHIK
INFORMATION TECHNOLOGY DEPARTMENT.
ACADEMIC YEAR 2021-22

“Software Engineering”(22413)

MICRO-PROJECT
ON
“Hotel Management System”
Guided By :-
Prof. R. S. More
SUBMITTED BY: -

SR. NO ENROLLMENT NO EXAM SEAT NO STUDENT NAME

1 2010020344 KATHE GAURAV

2 2010020345 KATORE POOJA

3 2010020346 KHAIRNAR SANJEEVANI

4 2010020347 KHALKAR PRANAV

1
 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION

Certificate

This is to certify that Ms./Mr. ________________________________________

Roll No._______ of Fourth semester of diploma in Information Technology of

Institute MVPS’s Rajarshi Shahu Maharaj Polytechnic, Nashik (Code: 1002) has

successfully completed micro-project in Software Engineering (22413) for academic

year 2021-22 as prescribed in curriculum of MSBTE, Mumbai.

Place: Nashik Enrollment no:……………..

Date:…………. Exam seat no:…………..

Prof. R. S. More Prof. N. A. Gade Dr. D. B. Uphade

Course Teacher/Guide I/c HOD, IF Principal

Seal of
institute

2
 Index

Sr.no. Chapter No. Chapter Name Page No.

1 - Abstract 4

2 1 Introduction 5

3 2 Problem Statement 6

4 3 Process Model 7

5 4 Requirements Analysis 9

6 5 Software Requirements Specifications 12

7 6 UML Diagram 16

8 - Conclusion 24

9 - References 25

Figure Index
Sr.No. Fig No. Fig Name Page no.
1 3.1 Incremental Model 7
2 3.2 Operating environment 13
3 4.1 Use Case Diagram 16
4 4.2 Activity Diagram For railway system 18
5 4.3 ER Diagram 19
6 4.4 DFD Level 0 Diagram 20

7 4.5 DFD level 1 Diagram 21

8 4.6 Sequence Diagram 22

9 4.7 Class Diagram 23

Abstract

3
 The Project Hotel Management System is a web based application that allows the hotel
manager to handle all hotel activities online. Interactive GUI and the ability to manage various
hotel bookings and rooms make this system very flexible and convenient. The hotel manager is a
very busy person and does not have the time to sit and manage the entire activities manually on
paper. This application gives him the power and flexibility to manage the entire system from a
single online system. The system aims at the maintenance and management of the different Hotels
that are available in the different parts of the world. It mainly takes care of the Hotel management
at the core area of the database. The system provides the information regarding the different
Hotels that are available and their status specific to availability. The guests can visit the site and
register themselves with the required information that is expected by the system. Each registered
guest can raise a request for the unit bookings. The Guests are scheduled with the information of
the availability of the units for they have requested the time.Hotel Management project provides
room booking, staff management and other necessary hotel management features. The system
allows the manager to post available rooms in the system. Customers can view and book room
online. Admin has the power of either approving or disapproving the customer's booking request

Keywords: Booking, payment, Security system, Hotel manager, administrator

Chapter 1

Introduction

Hotel Management System is a system that provides us to reserving rooms, checking

whether the rooms are vacant are or not etc by using online browsing. This system is very useful
to all especially for business people. For Business people they don’t have sufficient time for
these then they can use these type of online Hotel Management Systems. By this project we will
reduce the faults in bills of their expenditure and decrease time of delay to give the bills to the
4
customers. We can also save the bills of the customer. By this project we can also include all the
taxes on the bills according to their expenditures. It has a scope to reduce the errors in making
the bills. Computerized bill can be printed within fraction of seconds. Online ordering of
Booking is possible by using this software. This Project is based on php. If any one wants to
book the room for few days then they can specify the specific number by seeing the types of
rooms we have. The bill of this online booking is based on the type of room they can select is
displayed.

Hotel management system is a hotel reservation site script where site users will be able to
search room’s availability with an online booking reservations system. Site users can also
browse hotels, view room inventory, check availability, and book reservations in real-time. Site
users enter check in date and check out date then search for availability and rates. After choosing
the right room in the wanted hotel – all booking and reservation process is done on the site and
an SMS is sent to confirm the booking.

Chapter 2

Problem Statement

Web application for Hotel reservation. We will take the selection criteria from user and
display the hotels list for user basing on the criteria. User can book the room if there is
availability of the rooms in that particular hotel. There are three different types of user roles for
the application they are administrator , hotel agent and normal user. Following are the actions
provided for each user.

5
 Adding Hotel information such as hotel name, location, number of rooms , facilities etc. to
the database. Listing the hotels based on different criteria selected by the user .User able to select
a hotel and book a room. Booking permitted only if there are rooms available Displaying the
reservation status. Registration of users. Update user details. Modify hotel details. Approval of
the details entered by the hotel agent. Delete user/hotel details by admin. This are some of the
minimal features of problem statement for hotel system.

Chapter 3

Process Model

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.

6
 Fig no.3.1 Incremental model

The various phases of incremental model are as follows:

1. Requirement analysis: In the first phase of the incremental model, the product analysis expertise
identifies the requirements. And the system functional requirements are understood by the requirement
analysis team. 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. When software develops new
practicality, the incremental model uses style and development phase.

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. After completion of this phase, the number of the product working is enhanced and
upgraded up to the final system product.

Advantages of Incremental Model

o Errors are easy to be recognized.
o Easier to test and debug
o More flexible.
7
 o Simple to manage risk because it handled during its iteration.
o The Client gets important functionality early.

Disadvantages of Incremental Model

o Need for good planning
o Total Cost is high.
o Well defined module interfaces are needed.

Reason The Incremental Model In Hotel Management System

Incremental model is adapted as a process model for development of Hotel management system.
Incremental model is choose for development of Hotel management system is because The
incremental model applies the waterfall model incrementally. The series of releases is referred to as
increments with each increment providing more functionality to the customers. After the first
increment, a core product is delivered, which can already be used by the customer. Based on
customer feedback, a plan is developed for the next increments, and modifications are made
accordingly. This process continues, with increments being delivered until the complete product is
delivered.

Chapter 4

Requirements Analysis

4.1 User requirements & Planning:

The following requirements are raised during the analysis of the needs of the users:
1. A simple user can access their account and can deposit/withdraw money from their account.
2. User can also transfer money from their account to any other bank account.
3. User can see their transaction report and balance enquiry too

I. System Planning

Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time
feasibility and operational feasibility for the project. Project Scheduling should be made using
PERT charts.

8
Feasibility study is carried out to decide whether the proposed system is feasible for the
company. The feasibility study is to serve as a decision document it must answer three key
questions:
1. Is there a new and better way to do the job that will benefit the user?
2. What are the cost and the savings of the alternative(s)?
3. What is recommended?

II. Technical feasibility:

Technical feasibility centres on the existing computer system i.e. Hardware, Software etc.
Hotel requires SQL database management that are all easily available with extensive
development support through manuals and blogs.

III. Economical feasibility:

Economical Feasibility is the most frequently used method for evaluating the effectiveness of a
candidate system. More commonly known as Cost. Benefit analysis, the procedure is to
determine the benefits and savings that are expected from the candidate system and compare
them with costs.

4.2 Functional Requirements:

A functional requirement defines the internal workings of the system: that is, the reservations,
technical details, data manipulation and processing, and other specific functionality that shows
how the use cases are to be satisfied. The functionalities of the system or modules are mean
what the system supposes to do.

For creating a booking

In order for the user to create a booking for a room on the system, they first to take the
customers personal details, these details consist of things such as First and Last Name, Phone,
address, email etc. Next the customer has to specify their room preferences in terms of room
size, room location and additional services, based on these criteria and on the availability of the
rooms the system will allocate the appropriate room for the customer and then present them
with the price. Once the customer confirms the details of the booking the member of staff in use
of the system can then proceed to place the booking. All these details will be filled out in a form
present within the system.

For Administrative function

Regular administrative functions will have to be carried out to ensure that the system is always
running as intended. These administrative functions range from regular supervision of the
system i.e. keep an eye on the bookings that are placed on the system, another administrative
function that is expected is to continuously monitor how the system is performing over its life
time, this means taking note of any bugs or faults within the system and ensuring that those bugs
are continuously reported to the development team.

4.3 Non-Functional Requirements:

Non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of a system, rather than specific behaviors. It is about how the system supposes
9
to be and specify the quality of the system, is mostly related to the satisfaction of the user,
example minimum acceptable page load time. Some of these non-functional requirements are:
1. Integrity
2. Usability
3. Maintainability

Integrity: Integrity testing is basically a type of software testing that is done to check whether
the application or the product is secured or not. It checks to see if this application is vulnerable to
attacks, if anyone hack the system or login to the application without any authorization. It is a
process to determine that an information system protects data and maintains functionality as
intended. The security testing is performed to check whether there is any information leakage in
the sense by encrypting the application or using wide range of software’s and hardware’s and
firewall etc. For example this railway system can allow the users to login and can reserve the
seat according to them. And can view the details according to them.

Usability: This has to do with black box testing, but relating it to white box testing, usability
testing is a very wide area of testing and it needs fairly high level of understanding of this field
along with creative mind. People involved in the usability testing are required to possess skills
like patience, ability to listen to the suggestions, openness to welcome any idea, and the most
important of them all is that they should have good observation skills to spot and fix the issues or
problems. As soon as the user problems are identified, if such problem arises from the internal
mechanism of the product then white box testing strategy can help to identify and fix those
problems

Maintainability: It basically defines that how easy it is to maintain the system. This means that
how easy it is to analyses, change and test the application or product. Maintainability testing
shall use a model of the maintainability requirements of the software product. The
maintainability testing shall be specified in terms of the effort required to effect a change under
each of the following four categories:

1. Corrective maintenance: Deals with correcting problems. The maintainability of a system

can be measured in terms of the time taken to diagnose and fix problems identified within that
system.

2. Perfective maintenance: This deals with system enhancements. The maintainability of a

system can also be measured in terms of the effort taken to make required enhancements to that
system. This can be tested by recording the time taken to achieve a new piece of identifiable
functionality such as a change to the database, etc. A number of similar tests should be run and
an average time calculated. The outcome will be that it is possible to give an average effort
required to implement specified functionality. This can be compared against a target effort and
an assessment made as to whether requirements are met.

3. Adaptive maintenance: Adapting to changes in environment. The maintainability of a

system can also be measured in terms on the effort required to make required adaptations to that
system. This can be measured in the way described above for perfective maintainability testing.

4. Preventive maintenance: Actions to reduce future maintenance costs. This refers to

actions to reduce future maintenance costs and to maximize profit while reducing cost. It also
important to note that maintainability deals with; modular structure of software, internal program
10
documentation, Programmers manual typical requirements, Code to company standards and
guidelines.

Chapter 5

Software Requirements Specifications

Description

1. Introduction:-
A system requirements analysis is a complete description of the behaviour of the system to be
developed. It includes a set of use cases that describe all of the interactions that the users will
have with the system. In addition to use cases, the system requirement analysis contains
functional requirements, which define the internal workings of the system: that is, the
calculations, technical details, data manipulation and processing, and other specific functionality
that shows how the use cases are to be satisfied. It also contains non-functional requirements,
which impose constraints on the design or implementation (such as performance requirements,
quality standards or design constraints).

11
 1.1. Purpose:-
The proposed system is a hotel management system which will allow for staff to view rooms
that are available and highlight rooms that have already been booked. The scope of the project
is to create a booking management system, which will have features such as highlighting
booked rooms, searching certain rooms and filters allowing for staff to book available rooms
in a simplified manner while providing a foundation for expandability with easy to read code
where another programmer can implement additional features

1.2. Document Conventions:-

The Document font convention is Arial and our typographical convention will be using bolding of
words to emphasize words which are of special significance. The requirements will be inherited by
higher-level requirements as the requirements can be generalized at the highest level and into the
lower levels, we can go into further detail on the requirements of each area within the system.

1.3. Intended Audience:-

The intended audience of this SRS consists of:-
i. Developers
ii. Manager
iii. Management people
iv. Counter clerk
v. Tester
vi. Specifically
vii. Customer

1.4. Project Scope:-

The software is a hotel management system, the purpose of the system is to create a program
which can be used for a hotel business which will have all the features that a hotel business
would need but also will be a platform for expandability which will allow a developer to add
additional features to the feature set.
2. Overall Project Description:-
2.1 Product Perspective:-

It will empower us to manage

the railway

12
train info like their journey
time, Arrival/Departure time,
Seat availability and
reservation billing and
cancellation of the tickets
It will empower us to manage
the railway
train info like their journey
time, Arrival/Departure time,
Seat availability and
reservation billing and
cancellation of the tickets
The system will allow for staff to be able to receive calls from customers who inquire about
bookings and want to book over the phone or cancel a booking and the staff will be able to do
that in the management system which improves efficiency of the whole system as customers
don’t have to inquire just through email about availability which takes several days to get a reply
whereas a customer can ring up and get an instant inquiry which can lead to a sale and that is
important to an organization that relies on the efficiency of systems to generate sales.

13
 2.2 User classes and characteristics:-
The user classes are listed below (high-low importance)
 Reception staff- Taking and receiving calls, managing the bookings.
 IT staff – Maintenance and safekeeping of the system.
 Human Resources- Training staff to use the system.
 Managing staff- using data from the system to produce reports on revenue.

2.3 Operating Environment:-

2.4 Assumptions and Dependencies:-

A phased method which consists of taking modules and implementing them into the older system
in pieces would have less risk of the system going wrong as if something goes wrong then that
part will be the only one affected and not the specific part, however, this takes a lot of time and
leads to difficulty in integrating the old and new systems as there may be compatibility issues.

2.5 Product Function:-

I. Staff must be able to check availability of a room.
II. Staff must be able to book or cancel a room.
III. Staff must be able to search through room numbers.
IV. Staff must be able to use the system to sort by room number and price.
V. Staff must be able to take customer details and complete a booking
3. External Interface Requirements:-

14
3.1 User Interface:-
The GUI will contain a search bar at the top of the program with a box which has a specific
result (e.g. search room number) underneath there will be a detailed search with filters such as
size, the price range with a slider and tick boxes that has extras and a sort by button which sorts
by room and price. The error messages will display simplistic messages the user can understand
and will include no jargon that the user would not be able to understand and without any
abbreviations further, we will use the appropriate command buttons which include ok, cancel,
yes and no and retry.

3.2 Hardware Interface:-

Nothing special Interface is required.
1. Touch screen/Monitor
2. Keypad
3. Continuous battery backup
4. Printer which can produce the hard copy.
5. An interface that can count currency notes.

3.3 Software Interface:-

1. Any windows operating system.
2. These products are open source products.
3. The final application must be packaged in a set up program, so that the products can be easily
installed on machines. This application must be networked to corresponding railways.

4. Other Non-Functional Requirements:-

4.1 Performance Requirements:-

One of the major performance requirements to take into consideration when designing the Hotel
Booking System is response time. The system has to be able to quickly respond to inputs and
requests from the user, any delays between the users inputs and the systems response (where
necessary) should be kept to a minimum i.e. retrieving customer information in regards to a
booking.

4.2 Safety Requirements:-

There are very few safety measures which can be taken into account with the system, other than
the loss of data, or damage of equipment which in fact is not a direct detriment to the system
itself, there aren’t too many safety requirements which can be noted. However with that said
there are still things which can be done to help prevent some of the risks outlined above, for
example retaining multiple backups of the system to help reduce the risk of loss or damage of
the data on the system.
4.3 Security Requirements:-
Some form of user login procedure will be implemented within the system to prevent
unauthorized personnel from accessing the system.  Any member with access to the system will
be expected to have a user name and pass word that enables them access to the systems facilities.

15
 Chapter 6
UML Diagrams
Use Case Diagram for Hotel Management System:-
16
 Fig no. 4.1 Use Case Diagram

In above Hotel management system project there are three users Administrator, Customer and
Reception.

Reception Activities:
• Check in time
• Check out time
• Ask for room check booking

Customer Activities:
• User log in
• Make booking
• Make payment
• Cancel booking
• Check room availability

17
 • View profile & gallery
Admin Activities:
• User log in
• Make booking
• Make payment
• Cancel booking
• Check room availability
• View profile & gallery
• Check in time
• Check out time
• Ask for room check booking
• Admin log in
• Manage & update database

 Activity Diagram For Hotel Management System :-

The activity diagram used to describe flow of activity through a series of actions. Activity
diagram is a important diagram to describe the system. The activity described as a action or
operation of the system.

18
 Fig No. 4.2 Activity Diagram for hotel management system

The activity diagram used to describe flow of activity through a series of actions. Activity diagram
is a important diagram to describe the system. The activity described as a action or operation of the
system

19
  ER Diagram For Hotel Management System :-

Fig No. 4.3 ER Diagram for hotel management system

• The details of Customer is store into the Customer tables respective with all tables
• Each entity (User, Login, Roles, Permission, Payments, Hotel, Booking, Customer)
contains primary key and unique keys.
• User has various attributes like ID, Name, Address, email, mobile.
• Login has attributes like username, id, password.
• Permission has attributes id, module, name..
• Payments has attributes like user id, id, date, amount, desc.
• Hotel has attributes like type, desc, name, rent, email id..
• Customer has attributes like add, name, mobile no, email, pass.

20
  Data Flow Diagram Level 0 For Hotel Management System :-

Fig No. 4.4 DFD Level 0 Diagram

This is Zero Level DFD of Hotel Management System. It’s a basic overview whole of the
Hotel Management system or process being analyzed and modelled. In this Zero Level We
have Sub Division like Hotel Administrator, Customers, Hotel Management, Employee.

21
  Data Flow Diagram Level 1 For Hotel Management System :-

Fig No. 4.5 DFD level 1 Diagram

This is level 1 where it goes one step forward and details about the functionality. It may
require more functionality to reach the level. The first level now requires detailed about the
records and updating of managements.

22
  Sequence Diagram For Hotel Management System :-

Fig No. 4.6 Sequence Diagram

Sequence diagram are sometimes called event diagram or event scenarios. A sequence
diagram shows, as parallel vertical lines, different processes or object that live simultaneously
and horizontal arrows, the message exchanged between them, in the order in which they
occur.

23
  Class Diagram For Railway Reservation System:-

Fig No.4.7 Class Diagram

Class diagram are generally used for conceptual modelling of static view of a software application,
and for modelling translating models into programming code in a detailed manner.
They are also used for data modelling on a widely use.

24
 Conclusion

We successfully completed our project Hotel Management Case study. We Understood

the Problem Statement and in this project we have represented the DFDs, Use cases, Activity
diagrams to make it more informative. We learnt to use the STAR UML SOFTWARE to draw
the diagrams. Hotel management helps in booking rooms and also gives detailed information
about hotel.

25
 References

1. Software Engineering for diploma 2018 edition

2. www.computer.org
3. Star UML Software
4. SEN Manual
5. https://itsourcecode.com/

26