Software Requirements

Specification
for

Hotel Management

Version 1.0 approved

Prepared by

S.M. Nevetha

E. Poovarasan

Sona College of Technology,

Salem.

30.01.2017
Software Requirements Specification for Hotel Management Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References.......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose

The Software Requirements Specification (SRS) will provide a detailed description of the
requirements for the Hotel Management System (HMS). This SRS will allow for a complete
understanding of what is to be expected from the newly introduced system which is to be
constructed. The clear understanding of the system 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 Hotel
Management System can be designed, constructed, and finally tested.
This SRS will be used by the system development team which is constructing the HMS and the
hotel end users. The Project team will use the SRS to fully understand the expectations of this
HMS to construct the appropriate software. The hotel end users will be able to use this SRS as a
"test" to see if the constructing team 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 team will
change the SRS to fit the end users' needs.

1.2 Document Conventions

HMS – Hotel Management System.

GUI – Graphical User Interface.
Bold-faced text has been used to emphasize section and sub-section headings.

1.3 Intended Audience and Reading Suggestions

This document is to be read by the development team, the project managers, marketing staff,
testers and documentation writers. The SRS has been organized approximately in order of
increasing specificity. The developers and project managers need to become intimately familiar
with the SRS.

1.4 Product Scope

The purpose of this specification is to document requirements for a system to book rooms
in our hotel by specifying date check in time checkout time along with number of adults and
number of children. The specification identifies what such a system is required to do. The
specification is written in a format conforming to the IEEE Standard 830-1984. Subject to approval,
Software Requirements Specification for <Project> Page 2

the specification will complete the Requirements phase and will be followed by detailed design,
implementation and testing.

The product will be labeled the Hotel Management System (HMS). The Hotel Management
System will provide user to allow access of our hotel rooms database that how many rooms are
available on the specified date and time. They can also check the details for number of adults and
children

2. Overall Description

2.1 Product Perspective

The HMS is designed to help the customers who book rooms in our hotel on a specified
date and number of persons. The current design goal is to build an internal system to achieve the
functionality outlined in this specification

2.2 Product Functions

The HMS will allow the user to book the rooms in our hotel on a specified date and
time(check in time and checkout time). They can also specify the number of adults and children
who need to occupy the room

HMS will have a login form which asks for the username and password to the user for the first
time they enter.

HMS allows multiple users access.

2.3 User Classes and Characteristics

This software is developed such that total appearance of the product to make it more user
friendly. 

2.3.1 Customer
Software Requirements Specification for <Project> Page 3

Remote customers most frequently use the device for finding rooms available in our hotel
and to book the rooms with specified number of adults and children. The customers are not
expected to have a high educational and proficiency level or technical expertise.

2.4 Operating Environment

Following are the requirements for running the software successfully-

 Processor – Pentium III or Higher.
 Ram – 512 MB or Higher.
 Disk Space – 10 GB or Higher.
 OS – Windows XP or Above.

2.5 Design and Implementation Constraints

 UI only in English.
 Login and password is used for identification of user and there is no facility for guest

2.6 Assumptions and Dependencies

The user is assumed to have basic knowledge of computers.

 The program will feature a simple point and click graphical Interfaces.
 The user is assumed to give the system right information regarding the room booking on
right date and time with correct number of persons
 The user is assumed to use this system for pre booking available rooms on specified date

3. External Interface Requirements

3.1 User Interfaces

Input from the user will be via keyboard input and mouse point and click. The user will
navigate through the software by clicking on icons and links. The icons will give appropriate
responses to the given input.

3.2 Hardware Interfaces

These are the minimum hardware interfaces-

 Processor – Pentium III or Higher.
Software Requirements Specification for <Project> Page 4

 Ram – 512 MB or Higher.

 Disk Space – 10 GB or Higher.

3.3 Software Interfaces

These are the minimum software interfaces-

 Technologies: PHP, CSS, HTML.
 Database: MYSQL
 Operating system: Windows XP or above.

3.4 Communications Interfaces

When a specific reservation reserved at the same time an e-mail notification will be sent to
both relevant staff member's e-mail account and guest's account. Guest will be notified in the
check-out date. To achieve that functionality, it requires having a stable internet connection.
Mostly a broadband connection with the client's computer will provide the efficient service.
Software Requirements Specification for <Project> Page 5

4. System Features

4.1 Login Page- a login page will ask for the username and password to the customer
during the first time they enter.

4.2 Customer information – Collects information about the customer like name, sex, age
etc.

4.3 Room Page – Type of room, facilities, amount, occupancies, and so on.

4.4 Payment page – Online payment including type of payment.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The performance of our software is at its best when the following are regularly done:
 Password Management
 Regular Database Archiving

5.2 Safety Requirements

Humans are error-prone, but the negative effects of common errors should be limited. e.g.
users should realize that a given command will delete data, and be asked to confirm their intent or
have the option to undo.

5.3 Security Requirements

Each member is required to enter an individual Username & password when accessing the
software. Administrators have the option of increasing the level of password security their
members must use. The data in the database is secured through multiple layers of Protection. One
of those security layers involves member passwords. For maximum Security of your software, each
member must protect their password.
Software Requirements Specification for <Project> Page 6

5.4 Software Quality Attributes

The Quality of the system is maintained in such a way so that it can be very user-friendly.
The software quality attributes are assumed as under:

 Accurate and hence reliable.

 Secured.
 Fast Speed.
 Compatibility