Hotel Management System

Software Requirements Specification

Document

Submitted To:

Ma’am Sammia Rauf

Submitted By:

Team Tension 
BSEF18A002 Hafiz Muhammad Ali
BSEF18A021 Hafsa Shaheen
BSEF18A031 Falaq ul Asbah
BSEF18A039 Rabia Arif

Version: 1 Date: 4/2/2021

Punjab University College of Information Technology, Lahore 1

 Table of Contents
1. INTRODUCTION
1.1 Purpose
1.2 Scope of the Project
1.3 Definitions, Acronyms and abbreviations
1.4 References
1.5 Overview

2. OVERALL DESCRIPTION
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 Constraints
2.5 Assumption and Dependencies

3. SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Software Interfaces
3.1.3 Hardware Interfaces
3.1.4 Communication Interfaces
3.2 Functional Requirements
3.3 Performance Requirements
3.4 Design Constraints
3.5 Software system attributes

1. INTRODUCTION

Punjab University College of Information Technology, Lahore 2

 The system aims at the maintenance and management of the Hotel. It mainly
takes care of the Hotel management at the core area of the database. The system
provides the information regarding the Hotel, the guests can visit the site and
register themselves with the required information that is expected by the system.
The Guests are scheduled with the information of the availability of the units for
they have requested the time. And also provides management staff of hotel to
regulate their manual work in a secured and easy system.

1.1 Purpose
This Hotel Management System Software Requirement Specification (SRS)’s
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.2 Scope of the Project

The HMS project is intended for the reservations for room that can be made
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 consist 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

Punjab University College of Information Technology, Lahore 3

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.3 Definitions, Acronyms and abbreviations
SRS Software Requirement Specifications
HMS Hotel Management System
DBMS Database Management System
Blueprint A design technical plan
JDBC Java Database Connectivity
HTTP/HTTPS Hyper Text Transfer Protocol/Secure
EJB Enterprise Java Beans
API Application Interface
OS Operating System
JSP Java Server Pages
RTM Requirement Traceability Matrix
FR Functional Requirement
NFR Non Functional Requirement
Subjective satisfaction The overall satisfaction of the system
End users The people who will be actually using the
system

1.4 References
i. Software Engineering 9th Edition, Ian Sommerville
j. Fundamentals of Database System, 6th Edition, Ramez Elmasri, Shamkant
B. Navathe
k. ER Diagram Tutorial:
https://www.tutorialspoint.com/dbms/er_diagram_representation.htm
l. Requirement Engineering:
http://morse.inf.unideb.hu/valseg/gybitt/07/ch02.html
m. Hotel Management System: https://www.scribd.com/doc/63824633/Hotel-
Management-System.
n. Case Study: https://www.scribd.com/doc/27927992/Hotel-Management-
Case-Study

Punjab University College of Information Technology, Lahore 4

 o. Data Flow Diagram: http://myyee.tripod.com/cs457/dfd.htm
p. Requirement Engineering:
https://en.wikipedia.org/wiki/Requirements_engineering

1.5 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 HMS from a general high level perspective.
The Specific Requirements section will describe in detail the requirements of the
system.

2. OVERALL DESCRIPTION
Describes m, 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 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 Functions

Our Product General functions are:
 Customer Registration

Punjab University College of Information Technology, Lahore 5

  Check for Availability Of Rooms
 Display the Rate
 Confirmation Of Booking
 Email Notification
 Payment (set rate, issue bills)
 Set Room Details
 Manage Booking Details
 Generate Report
 Customer Service
 Retrieve Reports (Staff payment, Income)
 Manage Users (Add, Update, Delete)
 Taking Backups
 Manage Guest (Add, Update Guest)
 Manage Room Details (Add, Update, Delete)
 Manage Staff (Add, Update,
 Delete, View)
 Manage Inventory (Add, Edit, Delete)

2.3 User Characteristics

There are 3 user Levels in our Hotel Management System:
A. Hotel Manager
B. Receptionist
C. Customers
Hotel Manager
Manager have every access to the hotel system. Manager is solely
responsible for managing hotel resources and staffs. Manager can view any report
such as financial report, customer information, booking information, and room
information, analyze them and take the decision accordingly. Manager also has
most of the privileges. Manger is required to have experience on managing hotel
previously, and have base knowledge of database and application server.

Receptionist
Hotel Receptionist sole purpose is to provide the quality customer service. He or
she have least access than manager. He or she can manage the booking details. He
or she can search for availability of rooms, add the customer, confirm the booking,

Punjab University College of Information Technology, Lahore 6

and update the booking details. Manager of hotel would probably want the
receptionist who have good communication skills and command over English
language. He or she should have basic IT Knowledge. 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.
Customer
Customer are vital part of the system. Customer have access to view the
vacant room information and price range. They should be able to confirm the
booking and cancel it if necessary. Customers have access to customer service desk
portal to forward their inquiry. Customer should at least be capable to use the web
UI interface.

2.4 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.
I. Memory: System will have only 10GB space of data server.
II. Language Requirement: Software must be only in English.
III. Budget Constraint: Due to limited budget, HMS is intended to very
simple and just for basic functionalities. UI is going to be very simple.
IV. Implementation Constraint: Application should be based on Java only.
V. Reliability Requirements: System should sync frequently to backup
server in order to avoid the data loss during failure, so it can be
recovered.
2.5 Assumption and Dependencies
It is assumed that system developed will work perfectly that’s going to be
developed under the Windows OS, and Apache Server with Mongo DB database.
If incase of any difficulties, SRS should be flexible enough to change accordingly.
- The system is required to save generated reports.
- Credit card payments are also included
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.

Punjab University College of Information Technology, Lahore 7

Otherwise if client use an open source operating system, there is a need of
changing the SRS accordingly.

3. SPECIFIC REQUIREMENTS

3.1 External Interface Requirements

3.1.1 User Interfaces
Login Log into the system as a Customer, Receptionist or Manager
Reservation Retrieve button, update/save reservation, cancel
reservation, modify reservation, change reservation, adjust room rate,
accept payment type/credit card
Check-in Modify room stay (e.g., new credit card), check-in customer
(with or without a reservation), adjust room rate, special requests,
accept payment type/credit card
Checkout Checkout customer, generate bill
Hotel Payment Accept payment for room and food
Room Service/Restaurant Create order, modify order, view order,
cancel order, generate meal bill
Customer Record Add or update customer records
Administer Rooms Availability and rates
Administer User Create, modify, and delete users; change password
Administer Meals Create, modify, and delete meal items and prices
Reports Select, view, save, and delete reports

3.1.2 Software Interfaces

1. Software is designed to run on any platform above Microsoft Windows 7 or
above (64-bit)
2. Microsoft .NET Framework

3.1.3 Hardware Interfaces

Monitor Processor RAM Disk Space

Punjab University College of Information Technology, Lahore 8

Resolution: Intel or AMD 4GB 4GB
2GHZ
1024x768

3.1.4 Communication Interfaces

The System shall be using HTTP/HTTPS for communication
3.2 Functional Requirements
1. Reservation/Booking
1.1. The system shall record reservations.
1.2. The system shall record the customer’s first name.
1.3. The system shall record the customer’s last name.
1.4. The system shall record the number of occupants.
1.5. The system shall record the room number.
1.6. The system shall display the default room rate.
1.7. The system shall record the customer’s phone number.
1.8. The system shall display whether or not the room is guaranteed.
1.9. The system shall generate a unique confirmation number for each
reservation.
1.10. The system shall automatically cancel non-guaranteed
reservations if the customer has not provided their credit card number
by 6:00 pm on the check-in date.
1.11. The system shall record the expected check-in date and time.
1.12. The system shall record the expected checkout date and time.
1.13. The system shall check-in customers.
1.14. The system shall checkout customers.
1.14.1. The system shall display the amount owed by the customer.

Punjab University College of Information Technology, Lahore 9

 1.14.2. To retrieve customer information the last name or room
number shall be used
1.14.3. The system shall record that the room is empty.
1.14.4. The system shall record the payment.
1.15. The system shall record customer feedback.
2. Food
2.1. The system shall track all meals purchased in the hotel.
2.2. The system shall record payment and payment type for meals.
2.3. The system shall bill the current room if payment is not made at
time of service.
2.4. The system shall accept reservations for food

3.3 Performance Requirements

● 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.4 Design Constraints

The Hotel Management System shall be a stand-alone system running in a
Windows environment

3.5 Software System Attributes

● Correctness: This system should satisfy the normal regular Hotel
Management operations precisely to fulfill the end user objectives

Punjab University College of Information Technology, Lahore 10

● Efficiency: Enough resources to be implemented to achieve the particular
task efficiently without any hassle.
● Flexibility: System should be flexible enough to provide space to add new
features and to handle them conveniently
● Integrity: System should focus on securing the customer information and
avoid data losses as much as possible
● Portability: The system should run in any Microsoft windows environment.
● Usability: The system should provide a user manual to every level of users.
● Testability: The system should be able to be tested to confirm the
performance and clients specifications.
● Maintainability: The system should be maintainable

Punjab University College of Information Technology, Lahore 11