National Textile University

Department of Computer Science

Subject:
Software Engineering Fundamentals
CSC-2073

Project:
SRS of “Hotel Managements System”

Submitted to:
Sir Dr. Muhammad Adeel

Submitted by:
Muhammad Ali Usman
Reg. number:
20-NTU-CS-1160
 Table of contents

1. Introduction
 Purpose
 Scope
 Definition, Acronyms, and Abbreviations
 Overview

2. Overall Description
 Product perspective
o Software interface
 Product Functions
 User characteristics
 Apportioning of Requirement
 Assumption of Dependencies
3. Specific Requirement
 External Interface
o User interface
o Software interface
o Hardware interface
o Communication interface

 Functional Requirements
 Nonfunctional Requirements
o Performance requirements

o Logical database requirements

o Design constraints

o Standards compliance

o Reliability

o Availability

o Security

o Maintainability

o Portability
 1. Introduction
The following subsection of the Software Requirements Specifications (SRS) document provide
an overview of the entire SRS.

 Purpose

The Software Requirements Specifications (SRS) will provide detailed

description of the requirements for Hotel Management System (HMS). The SRS
will allow for a complete understanding of what is to be expected of the HMS to
be construct. The clear understanding of the HMS 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 HMS can be designed, constructed
and finally tested.
This SRS will be used by the software engineers constructing the HMS and the
hotel end users. The software engineers 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 software engineers will
be constructing the system to their expectations. If it is not to their expectations
the end user can specify how it is not to their liking and the software engineering
will change the SRS to fit the end users’ needs.

 Scope
The software product to be produced is a Hotel Management System Which will
automate the project hotel operations. The First Subsystems is a reservation and
Booking System to keep track of reservations and room availability. The second
Subsystem is the Tracking and selling Food System and charges the current room.
The third Subsystem is a General Management services and automated tasks
system which generate reports to audit all hotel operation and allow modification
of subsystem management information. These are three subsystem and
functionality will be describing in the detail in session-2 Overall description.
There are two end user for the the HMS. The end user is the hotel staff (Customer
Services representatives) and hotel manager. Bothe user can access the
Reservations and Booking system will be restricted to management users.
The hotel management system’s objectives are 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 unwieldly task. The end users’ day-to-
day job of managing a hotel will be simplified by a considerable amount through
the automated system. The system will be handle to many services to take care of
all customers in a quick manner. The system should be appropriate, easy to use,
 provide easy recovery of errors and have an overall end user high subjective
satisfaction.

 Definition, Acronyms, and Abbreviation

SRS – Software Requirements Specification

HMS – Hotel Management System
Subjective satisfaction- The overall satisfaction of the System
End User- The people who will actually using the system

 Overview

The SRS is organized into 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
Requirement section will Describe in detail the requirements of the system.

2. Overall Description
Describe 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.

 Product perspective
The HMS is an independent stand-alone system. It is totally
self-contained.
 Hardware Interface: The HMS will be placed on PC’s throughout the hotel.
 Software Interface: All Database for HMS will be configured using MySQL.
The database includes hotel rooms and customer’s information. These can be
modified by the end users. The room database will include the room number and
if the they are vacant or occupied. The customer’s information database will
contain all the information of the customers such as first name, last name, number
of occupants, assigned room, default room rate (may be changed), phone number,
automatic cancellation date, expected checks in date and time, actual check in
date and time, expected check out date and time, amount owed by customer, and
abbreviated customer feedback.
 Product function
 future occupancy, room revenue, and food revenue.
 Expectation reports listing expectations to the normal cost
 Allows addition, delete, and modification of information on
rooms and rates, menu items and prices, user profiles.
Creation of users and assigning password Reservation and Booking system
 Allows for typing in customer’s information
 Has a default room rate that is adjustable?
 Include a description field for the changed rate
 When a customer’s checks in, the room number will be changed to occupied
in the data base
 Ability to modify a reservation
 When no rooms are available some customers would like to extend their
reservation their information will be placed in a database and when there are
rooms available the first customer on the list will have room.
 When the customer checked out the amount owed is displayed.
 If the internal clock states that is customer’s time to have checked out and
customer has not checked out, adds an extra night to amount owed and
provides a report.
 Records that room is vacant
 Record payment
 Allows for spaces to write customer’s feedback
Tracking and selling food system
 Track all meals purchased
 Charges the current room as necessary
General management services and automated task system
 Reports generated to audit hotel occupancy

 User characteristics

Educational level of HMS computer software-low

Experience of HMS software – None
Technical Expertise – Little

 Apportioning of requirements

The audio and visual alerts will be deferred because low importance of
this time.
 Assumptions and Dependencies

- The system is not required to save generated reports.

- Credit and payment not included.

3. Specific requirements
This section contains all the software requirements at the level of the detail, that when
combined with system context diagram, use case diagram, use case description, is
sufficient to enable designer design a system to satisfy those requirements, and tested to
test that the system satisfied those requirements.

 External Behavior

The hotel management system will use the standard input/output devices
for a personal computer. This include following

 Keyboard
 Mouse
 Monitor
 Printer

o user interface

The user interface describes in following:

 log in
 Reservation
 Check in
 Check out
 Hotel payment
 Room services restaurant
 Customer record
 Administrator room
 Administrator user
 Administrator meal
  Reports

o Software interface
The system shall interface oracle or access database.

o Hardware interface

The system shall run on Microsoft windows based system.

o Communication interface

The system shall be standalone product that does not required

any communication interface.

 Functional requirements
Functional requirements explain the functional actions that the system
must perform. The functional requirements of the system is divided into three
categories Reservation/Booking, Food and management for the further detail refer
to the use case.

o Reservation/Booking

 The system shall record the reservation.

 The system shall record customer first name.
 The system shall record customer last name.
 The system shall record the number of occupant.
 The system shall record the room number.
 The system shall display the default room rate.
- The system shall allow to change default room rate.
- The system shall require a comment to be enter why room
rate is change?
 The system shall record the customer phone number.
 The system shall display weather the room is guaranteed or not.
 The system shall generate a unique conformation number for every
reservation.
  The system shall check in customer.
 The system shall check out customer.
 The system shall charge the customer extra one night if they
customer checks out after 11:00 am.
 The system shall record the customer feedback.
o Food

 The system shall track all the meal purchased in hotel.

 The system shall record all the payment and payment type.
 The system shall bill the current room if the payment is not made
at time of services.
 The system shall accept for restaurant and room services.

o Management

 The system shall display project occupancy of period of time.

 The system shall display room revenue for a specific time.
 The system shall display food revenue for a specific time.
 The system shall display an expectation report, showing where
default room and food prices have been overridden.
 The system shall allow manager to assign user password.

 Non-Functional Requirements

Functional requirements define the needs in the term of performance, logical

database requirements, design constraints, standards compliance, reliability,
availability, security, maintainability, and portability.

o Performance requirements

Performance requirements define acceptable response time for system

functionality.
  The load time for user interface screen shall take no longer than
two seconds.
 The log in information shall be verified within five second.
 Quires shall return results within five seconds.

o 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 time
 Expected check in date
 Actual check in date
 Actual check in time
 Expected check out date
 Expected check out time
 Actual check out date
 Actual check in time
  Customer feedback
 Payment received
 Payment type

Food services

 Meal
 Meal type
 Meal order
 Meal payment

o Design constraints

The whole management system shall be s stand-alone system

running in a windows environment. The system shall be developed
using java and an access or oracle database.

o Standards compliance

There shall be consistency in variable names within the system.

The graphical user interface shall have a consistent look and feel.

o Reliability

Specify the factors required to establish the required reliability of

the software system at time of delivery.

o Availability

The system shall be availability during normal hotel operating

hours.

o Security

The system shall be secure. Software secure the database of the

system which contain all information.
o Maintainability

The HMS is being developed in java. Java is an object oriented

programming language and shall be easy to maintain.
o Portability

The HMS shall run in any MS window environment that contain

java runtime and the MS access database.