SRS for Hotel

Management System

Made By- 1. Adarsh Singh

Sem-Fifth, Sec-A, Roll No.-17

2. Aadarsh Chourasia

Sem-Fifth, Sec-A, Roll No.-15

 Table of Contents

1. Introduction

1.1 Purpose

1.2 Document Convention

1.3 Intended Audience and Reading Suggestions

1.4 Project Scope

1.5 References

2. Overall Description

2.1 Product Perspectives

2.2 Product Features

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 Assumptions and Dependencies

3. Functional and Non-Functional Requirements

3.1 Functional Requirements

3.2 Non-Functional Requirements

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.

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
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
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
The document is prepared using Microsoft Word 2013 and has used the font type 'Times
New Roman'. The fixed font size that has been used to type this document is 12pt with
1.5 line spacing. It has used the bold property to set the headings of the document. Use
case scenario is written according to Alistair Cockburn’s template. UML diagrams have
been created according to UML 2.0 standards. Standard IEEE template is the template
used to organize the appearance of the document and its flow.

1.3 Intended Audience and Reading Suggestions

The intended audience of this document would be owner and specific employees like
Manager and Receptionist of any particular hotel, and project team with the objective
to refer and analyze the information. The SRS document can be used in any case
regarding the requirements of the project and the solutions that have been taken. The
document would final provide a clear idea about the system that is building. Brief
outline of the document is,

1. Overall Description

2. System Features

3. External Interface Requirements

4. Non Functional Requirements

1.4 Project Scope

The introducing software, Hotel Management System which is going to be implemented

for, lets take an example, Hotel Gayana will automate the major operations of the hotel.
The Reservation System is to keep track in room and hall reservation and check
availability. The Room Management System is for manage all room types room services.
The Inventory Control System will keep track in all inventories of the hotel and guest
details will handled by guest management. Administration department will monitor the
 all .There is three End Users for HMS. The End Users are Owner, Manager and
Receptionist. Owner can access to all system functionalities without any restrictions.
Manager can access to all system functionalities with limited restrictions. Receptionist
can only access to the Reservation management section. To keep restrictions for each
End User levels HMS can create different Login functions. The objectives of the
automated Hotel Management System is to simplify the day to day processes of the
hotel. The system will be able to handle many services to take care of all customers in a
quick manner. As a solution to the large amount of file handling happening at the hotel,
this software will be used to overcome those drawbacks. Safety, easiness of using and
most importantly the efficiency of information retrieval are some benefits the
development team going to present with this system. The system should be user
appropriate, easy to use, provide easy recovery of errors and have an overall end user
high subjective satisfaction.

1.5 References

Books:

[1] IanSommerville,Software Engineering 8th edition.Pearson education,2008.

[2] ElmasriNavathe,Fundamentals of Database System 3rd edition.Pearson

education,2000.

[3]RaguRamakrishnan/JohnesGehrke,DatabaseManagementSystems
3rdedition.McGrowHILL,2003.

[4] Gerald W. Latin, Modern hotel management, W.H.Freeman, 2011.

[5] Michael J. O'Fallon, Denney G. Rutherford, Hotel Management and Operations

illustrated edition, John Wiley & Sons, 2001

World Wide Web:

[6]”Hotel Management Case Study”, March.6, 2010. [Online].Available:

http://www.scribd.com/doc/27927992/Hotel-Management-Case-Study,[Accessed:
June.28, 2014]

[7]”High-Level-SoftwareFeatures”,[Online].Available:http://www.high-level-
software.com/features/, [Accessed: June.25, 2014]

[8]Fernandez & Yuan, X,(1999). An analysis Pattern for Reservation and Use of Reusable
Entities.http://hillside.net/plop/plop99/proceedings/Fernandez2/reservanalysisPattern3
.PDf
 [9]Lauesen, S, (2003), Task Descriptions as Functional Requirements, IEEE Computer
Society, Retrieved from http://www.itu.dk/~slauesen/Papers/IEEEtasks.pdf

2. Overall Description
2.1 Product Perspective

The Hotel Management System is a new self-contained software product which will be
produced by the project team in order to overcome the problems that have occurred
due to the current manual system. The newly introduced system will provide an easy
access to the system and it will contain user friendly functions with attractive
interfaces. The system will give better options for the problem of handling large scale of
physical file system, for the errors occurring in calculations and all the other required
tasks that has been specified by the client. The final outcome of this project will increase
the efficiency of almost all the tasks done at the Hotel in a much convenient manner.

2.2 Product Features

 Make Reservations
 Search Rooms
 Add Payment
 Issue Bills
 Manage Guest (Add, Update Guest)
 Manage Room Details (Add, Update, Delete)
 Manage Staff (Add, Update, Delete, View)
 Manage Inventory (Add, Edit, Delete)
 Set Rates
 Retrieve Reports (Staff payment, Income)
 Manage Users (Add, Update, Delete)
 Taking Backups
 E-mail notifications

2.3 User Classes and Characteristics

These are the user classes in Hotel Management System

 User
 Chef
 Room Attendant
 Financial Manager
  Owner
 Manager
 Receptionist

Characteristics of User Classes

User:- The User can login into the system and book/cancel room reservations. He can
also order food by looking up the menu uploaded into the system or ask for cleaning
services. He can check in and check out virtually without the hassle of going to the front
desk for every little thing. He can also make payment through various payment portals
available in the system.

Chef:- The Chef gets notified whenever a User orders food and food preparations begin
right away. After the food has been prepared, he notifies the room service for delivery
of food so that the User’s order reaches his room at the earliest.

Room Attendant:- Each Room Attendant is assigned multiple rooms and gets notified
whenever user posts a request ranging from taking the baggages from his vehicle to his
room, cleaning to asking for some commodity. He also delivers the food from the
kitchen to the User’s room.

Financial Manager:- The Financial Manager looks over the finances of the hostel right
from booking room to asking for food and User can either pay in advance to avail
discount options or pay the lump sum at the time of his check out.

Owner:- Hotel owner has the privilege of Monitoring and authorization of all the tasks
handle by the system. He can access every function performed by the system. Owner of
the company as well as the system can access to the administration panel which is
consider the core of the system. As the main authorized person of the company owner
gets the ability to manage the other users including their user levels and privileges.
Taking backups of the system and restoring system can also be done by the Owner.
Meanwhile he will be able to take all the kinds of reports available in the system. As the
owner of the system and the company he has the power to set room rates as well. Hotel
owner has the sole right of deleting a staff member from the system database.

Manager: Manager is responsible for managing resources available in hotel

management system. Manager also has most of the privileges mentioned above except
the things regarding the payment handling. The reason for using a Manager is to
reduce the work load done by the owner that cannot be assigned to the receptionist, as
those tasks seem much responsible. The user level, Manager has the authority to take
 all the reports available in the system but here also except the reports related to
financial stuff, hotel income. Manager has other abilities that receptionist, user level
has. Such as, adding new staff member to the system, Modifying them or removing
them, Adding new guests to the system, Modifying them and removing them from the
system, Adding new inventory to the system, Modifying them and removing them.
Adding new room types to the system, modifying them and removing them.

Receptionist: As a hotel receptionist, he or her role will be to attain the goals of

bookings and to ensure that all guests are treated with a high standard of customer
service. Hierarchically receptionist role has the least accessibility to the system
functions. Receptionist plays the boundary role of the system .He or she can perform
limited functions such as registering new guest to the system, make reservations,
Sending e-mail reminders to clients for booking confirmation. Management of hotel will
prefer to hire receptionist who have a good standard of general education and possibly
in subjects such as English, math and IT.

2.4 Operating Environment

Hardware and software requirements

Hardware:-

1.Operating System Supports all known operating systems, such as Windows, Linux

2.Computer 512MB+ RAM, monitor with minimum resolution of 1024x768, keyboard,

and mouse

3.Hard Drive should be in NTFS file-system formatted with minimum 10 GB of free space

4.A Laser printer will need to be used to print these reports and notes

Software:-

1.Software is designed to run on any platform above Microsoft Windows 7 (32bit).

2.Microsoft .NET Frameworks 4.0 or above.

3.Microsoft SQL Server Management Studio Express 2010.

2.5 Design and Implementation Constraints

Software development crew provides their best effort in developing the system. In order
to maintain the reliability and durability of system, some design and implementation
constraints are applied. Availability of an android app for hotel management system
 could make the system portable but due to time constraint it is not possible. System will
need a minimum memory of 512MB. But it is recommended to have a memory of 1GB.
When designing interfaces of system, we had the capability of work with new tools such
as Dev Express. Considering the client’s budget we decided to create those
interfaces in a simple realistic manner using affordable technology.

2.6 Assumptions and Dependencies

Some software used in implementing the system is with high cost and the client has
agreed to afford the amount of money needed to purchase them. It’s assumed that
client won’t change that decision on the next phases of the software development.
Although we assume that client is using windows 7 or windows 8. Otherwise if client use
an open source operating system, there is a need of changing the SRS accordingly.

3. Functional and Non-Functional Requirements

3.1 Functional Requirements

 Associate every online booking with an account

 Limit every account to a single user
 Enable users to search and find most relevant
 Booking confirmation should be sent to specified contact details
 Calculate and Display accommodation charges
 Cancel bookings
 Change rooms
 Order food
 Display and change record of guests

3.2 Non-Functional Requirements

 Use encryption and captcha to avoid bots from booking

 Search results should populate within acceptable time limits
 Users should be helped appropriately to fill in mandatory fields in case of
invalid input
 System should accept payment via various payment methods
 Easy to use, efficient and accessible
 Keep track of documentation, activities and responses