www.studentprojectguide.

com

Hotel Management System

Software Requirements Specification

Document
 Hotel Management System Software Requirements Specifications (SRS)

Table of Contents

1 Introduction 4

1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations. 5
1.4 Overview 5

2 The Overall Description 5

2.1 Product Perspective 5

2.1.1 Hardware Interfaces 5
2.1.2 Software Interfaces 5
2.2 Product Functions 5
2.3 User Characteristics 6
2.4 Apportioning of Requirements. 6
2.5 Assumptions and Dependencies 6

3 Specific Requirements 7

3.1 External Interfaces 7

3.1.1 User Interfaces 7
3.1.2 Software Interfaces 7
3.1.3 Hardware Interfaces 7
3.1.4 Communication Interfaces 8
3.2 Functional Requirements 8
3.3 Nonfunctional Requirements 100
3.3.1 Performance Requirements 100
3.3.2 Logical Database Requirements 100
3.3.3 Design Constraints 111
3.3.4 Standards Compliance 111
3.3.5 Reliability 111
3.3.6 Availability 111
3.3.7 Security 111
3.3.8 Maintainability 11
3.3.9 Portability 111

Page 2 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

1 Introduction
The following subsections of the Software Requirements Specifications (SRS) document
provide an overview of the entire SRS. The Software Requirements Specification (SRS)
will provide a detailed description of the requirements for the Hotel Reservation System.
This SRS will allow for a complete understanding of what is to be expected of the HMS
to be constructed. The clear understanding of the HRS and its functionality will allow for
the correct software to be developed for the end user and will be used for the
development of the future stages of the project. This SRS will provide the foundation for
the project. From this SRS, the HRS can be designed, constructed, and finally tested.

This SRS will be used by the software engineers constructing the HRS and the hotel end
users. The software engineers will use the SRS to fully understand the expectations of
this HRS to construct the appropriate software. The hotel end users will be able to use
this SRS as a “test” to see if the software engineers will be constructing the system to
their expectations. If it is not to their expectations the end users can specify how it is not
to their liking and the software engineers will change the SRS to fit the end users’ needs.

1.1 Purpose
Samfas hotel offers Room facilities, Hall facilities, Gym facilities, Beauti parlor and spa
spa and other services. The existing system is the software application and not providing
any features like Online room booking, hall booking, event registration, etc. And an
existing system is not user friendly. The development of the new system will automate
the entire process of the hotel. In the new system, the customers can make searches,
reservations and cancel an existing reservation on the hotel reservation's web site. The
Online Hotel Reservation system will provide service to online customers, employees,
and administrator. Administrator can add or update the hotel and room information,
Employee details, Room tariff details, Hall details, and other services offered by hotel.

The Hotel Management System’s objectives is to provide a system to manage a hotel that
has increased in size to a total of 100 rooms. Without automation the management of the
hotel has become an unwieldy task. The end users day-to-day jobs of managing a hotel
will be simplified by a considerable amount through the automated system. The system
will be able to handle many services to take care of all customers in a quick manner. The
system should be user appropriate, easy to use, provide easy recovery of errors and have
an overall end user high subjective satisfaction.

1.2 Scope
The website product to be produced is a Hotel Reservation System which will
automate the major hotel operations. The first subsystem is a Reservation and Booking
System to keep track of reservations and room availability. The second subsystem is the
General Sevice offered by hotel ie; Hall facilities, Gym facilities, Beauty parlour and spa

Page 3 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

and other services. In the third subsystem is the system will generate reports. These three
subsystems functionality will be described in detail in section 2-Overall Description.

There are two end users for the Hotel Reservation System. The end users are the
customers and hotel management(Admin and Employees). Both user types can access
the Reservation and Booking System and the Food Tracking and Selling System. Some
authorities are restricted to the customers.

1.3 Definitions, Acronyms, and Abbreviations.

SRS – Software Requirements Specification
HRS – Hotel Reservation System
End users – The people who will be actually using the system
PHP – PHP: Hypertext preprocessor
1.4 Overview
The SRS is organized into two main sections. The first is The Overall Description
and the second is the Specific Requirements. The Overall Description will describe the
requirements of the HRS from a general high level perspective. The Specific
Requirements section will describe in detail the requirements of the system.

2 The Overall Description

Describes the general factors that affect the product and its requirements. This section
does not state specific requirements. Instead it provides a background for those
requirements, which are defined in section 3, and makes them easier to understand.

2.1 Product Perspective

The HMS is web portal. All databases for the HRS will be configured using MySQL
database. These databases include hotel rooms, customers information, billing details and
other service information. These can be modified by the end users.

2.1.1 Hardware Interfaces

Operating system: Windows XP/Windows 7/ Windows 8
Processor: Pentium- II or higher
Hard Disk Space: 40 GB (min.)
RAM Memory: 512 MB (Min)

2.1.1 Software Interfaces

XAMPP Software v 3.2.1
Apache server 1.8.2
MySQL database Server 5.5
IDE: Adobe Dreamweaver
Browser: Google chrome or Mozilla firefox or Internet explorer

Page 4 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

2.2 Product Functions

First sub system: Reservation and Booking System
 This website allows customers to book rooms through online by entering customers
profile information and room details.
 During the booking process, customer can see available rooms for the desired period and will
have the opportunity to select one or more rooms as well as the number of guests in each room.
 The customers information will contain all the information of the customer such as first
name, last name, number of occupants, room details, phone number, payment details, check in
date and time, check out date and time, total amount, etc.
 Room reservation management module allows hotel managers and staff to add bookings
manually, change reservation details and issue invoices.
 Allows addition, deletion and modification of information on rooms, tariff rates and room
type for administrator.
 Admin can define individual room number for each room that they manage.
 The system wil dispay realtime records which provides customers and staff with a quick
visual to room availability and bookings.
 It has two types of payment options i.e; cash payment and credit card payment.

Second sub system: General Service management system

Hall booking: Through this option the customers can view different types of hall
and rates online. To book the hall, the customer must register their profile and
specify the Hall name, date, etc.

Third sub system: Report management system

 The management or customer can generate billing or invoice report.

2.3 User Characteristics

Educational level of HRS computer software – Low
Experience of HRS software – None
Technical Expertise – Little

2.4 Apportioning of Requirements

The audio and visual alerts will be deferred because of low importance at this time.

2.5 Assumptions and Dependencies

- The system is not required to save generated reports.
- The Cash payment and Credit card payment is only for testing purpose and it’s a virtual
payment gateway.

Page 5 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

3 Specific Requirements
This section contains all the software requirements at a level of detail which enables
designers to design a system to satisfy those requirements and testers to test that the
system satisfies those requirements.

3.1 External Interfaces

The Hotel Reservation System will use the standard input/output devices for a personal
computer. This includes the following:
 Keyboard
 Mouse
 Monitor
 Printer

3.1.1 User Interfaces

The User Interface Screens are described below.
Screen Name Description
Login Log into the system
Reservation Save reservation, cancel reservation, modify reservation, change
reservation, adjust room rate, accept payment type credit card
Check-in Modify room stay , check-in customer (with or without a
reservation), adjust room rate, accept payment type/credit card
Checkout Checkout customer, generate bill
Customer Record Add or update customer records
Administer Rooms Availability and rates
Administer User Create, modify, and delete users; change password
Reports Select, view, save, and delete reports

3.1.2 Software Interfaces

The system shall interface with an MySQL Database.

3.1.3 Hardware Interfaces

The system shall run on a browsers like Google chrome, Mozilla firefox, Internet
explorer.
3.1.4 Communication Interfaces
Internet connection is required
3.2 Functional Requirements

Page 6 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

Account module: In this module online customer can register by entering name, email
id, contact number, address, login id, password, etc. After the registration customer can
login to the hotel reservation website by entering login id and password.

Branch module: This module is for administrator to add new branch records.

Rooms module: In this module administrator can add rooms and it has options to add
different types of rooms.

Health club module: In this module customer can book date and time.

Swimming pool module: In this module customer can book date and time.

Spa and Beauty parlour: In this module customer can book date and time and they can
select the different services provided by spa and beauty parlour.

Events module: In this module customer can book halls by entering date and time. Even
cutstomers can select services like sound systems, food items, etc.

Catering module: This module is for caterers to delivered ordered foods.

Travel module: This module is for customer where customer can book a car for rent.

Payment module: The customer can make payment for the bill.

Dashboard module: This module is for administrator where administrator can add
different room types, room details, room tariff details, hall details, etc.

Page 7 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

3.3 Nonfunctional Requirements

Functional requirements define the needs in terms of performance, logical database
requirements, design constraints, standards compliance, reliability, availability, security,
maintainability, and portability.

3.3.1 Performance Requirements

Performance requirements define acceptable response times for system functionality.
 The load time for user interface screens shall take no longer than two seconds.
 The log in information shall be verified within five seconds.
 Queries shall return results within five seconds.

3.3.2 Logical Database Requirements

The logical database requirements include the retention of the following data elements.
This list is not a complete list and is designed as a starting point for development.

Booking/Reservation System
 Customer first name
 Customer last name
 Customer address
 Customer phone number
 Number of occupants
 Assigned room
 Default room rate
 Rate description
 Guaranteed room (yes/no)
 Credit card number
 Confirmation number
 Automatic cancellation date
 Expected check-in date
 Expected check-in time
 Actual check-in date
 Actual check-in time
 Expected check-out date
 Expected check-out time
 Actual check-out date
 Actual check-out time
 Customer feedback
 Payment received (yes/no)
 Payment type
 Total Bill

Page 8 of 9 f
 Hotel Management System Software Requirements Specifications (SRS)

3.3.3 Design Constraints

The Hotel Reservation System is the web portal. The system shall be developed using
PHP and MySQL database.

3.3.4 Standards Compliance

There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.

3.3.5 Reliability
Specify the factors required to establish the required reliability of the software system at
time of delivery.

3.3.6 Availability
The system is online web application and user can access in any latest browser.

3.3.7 Security
The system has encrypeted password.

3.3.8 Maintainability
The Hotel Reservation System is being developed in PHP. PHP is an object oriented
programming language and shall be easy to maintain.

3.3.9 Portability
The Hotel Reservation System shall run in any Operating system that latest browsers.

Page 9 of 9 f