

Software Requirement Specification

On
HOTEL MANAGEMENT SYSTEM

SUBMITTED BY:
Neha 4nm20is087
Pratheeksha R 4nm20is104
INDEX:

1. INTRODUCTION

1.1 SCOPE

1.2 OVERVIEW

2. SPECIFIC REQUIREMENTS

2.1 FUNCTIONAL REQUIREMENTS

2.2 NON FUCTION REQUIREMENTS

3. SYSTEM ARCHITECTURE

4. USE CASE DIAGRAM

5. CONCLUSION
1. INTRODUCTION:
The Hotel Management System is a tool
for booking the rooms of Hotel through online by
the Customer. It provides the proper management
tools and easy access to the customer information.
This Hotel Management System Software
Requirement Specification (SRS) main objective is
to provide a base for the foundation of the project.
It gives a comprehensive view of how the system
is supposed to work and what is to be expected by
the end users. Client’s expectation and
requirements are analyzed to produce specific
unambiguous functional and non-functional
requirements, so they can be used by development
team with clear understanding to build a system as
per end user needs.
This SRS for HMS can also be used for
future as basis for detailed understanding on how
project was started. It provides a blueprint to
upcoming new developers and maintenance teams
to assist in maintaining and modifying this project
as per required changeability.
1.1 SCOPE:
The HMS project is intended for the reservations
for room that can be made through online. It will be
able to automate the various operations of the Hotel.
Our Hotel Management System will have three end
users: Customer, Receptionist, and Hotel Manager.
Hotel Management System will consists of Booking
Management System, DBMS Server, and Report
Generator. Customers will be able to check for room’s
availability, select the rooms, and pay for the room.
Receptionist will have access to update or modify
booking details. Manager will able to view the financial
report and able to update room information such as cost
and category.
The main goal of this introduced automated
HMS software is to simplify every day process of hotel.
Day to day Hotels are increasing and they need to
automate to provide customer ease of access. It will be
able to take care of services to customer in a quick
manner. This automation will be able to replace the
drawbacks of large customer information physical files
which were difficult to handle. Secure Transaction,
quick retrieval of information, ease of use, quick
recovery of errors, fault tolerance are some of the
benefits that development team will be working on to
achieve end user satisfaction.

1.1 OVERVIEW:
The remaining sections of this
documentations describes the overall descriptions
which includes product perspective and functions,
characteristics of users. It also consists of
Assumptions, and Constraints. Overall description
is listed in section 2. Section 3 includes Specific
Requirements which consists of Functional and
Non-functional requirements, External Interface
Requirements, Software System Attributes,
Performance Requirements, Capacity
Requirements, Availability Requirements, Safety
Requirements and Requirement Traceability
Matrix.
2. SPECIFIC REQUIREMENTS:
2.1 FUNCTIONAL REQUIREMENTS
Functional requirements capture the intended
behaviour of the system. This behaviour may be
expressed as services, task or functions the system is
required to perform.
Following are the required features of this project:
Reservation/Booking
record reservations
record the customer’s first name
record the customer’s last name
record the number of occupants
record the room number
display the default room rate 
record the customer’s phone number
display whether or not the room is guaranteed 
generate a unique confirmation number for each 
record the expected check-in date and time
The system shall record the expected checkout date and time
The system shall check-in customers
The system shall allow reservations to be modified without having to
reenter all the customer information
The system shall checkout customers
The system shall charge the customer for an extra night if they
checkout after 11:00 am.The system shall mark guaranteed rooms as
“must pay” after 6:00 pm on the check-in date.
The system shall record customer feedback

Food:
The system shall track all meals purchased in the hotel (restaurant and
room service).
The system shall record payment and payment type for meals
The system shall bill the current room if payment is not made at time
of service
The system shall accept reservations for the restaurant and room
service.

 Management
display the hotel occupancy for a specified period of time (days;
including past, present, and future dates).
display projected occupancy for a period of time (days).
display room revenue for a specified period of time (days).
display food revenue for a specified period of time (days).
display an exception report, showing where default room and food
prices have been overridden
allow for the addition of information, regarding rooms, rates, menu
items, prices, and user profiles
allow for the deletion of information, regarding rooms, rates, menu
items, prices, and user profiles
allow for the modification of information, regarding rooms, rates,
menu items, prices, and user profiles
allow managers to assign user passwords