VISION

FOR

HOTEL MANAGEMENT SYSTEM

Version1.0

Prepared By
M. Usman Haider
&
Zain Tariq

16 Aug, 2020
 Revision History

Version Description Author Date

Zain Tariq
First Release/
1.0 16 Aug, 2020
initial release Muhammad Usman Haider
 1. Introduction

1.1 Project Summary

This is software for managing the general activities of a hotel like booking of rooms, billing etc. The
purpose of this document is to collect, analyze and define high-level needs and features of the Hotel
Management System. It focuses on the capabilities needed by the stakeholders, and the target users,
and why these needs exist. The details of how the Hotel Management System fulfills these needs are
detailed in the use-case and supplementary specifications.

1.2 Purpose
This software is aimed at facilitating the prompt, accurate and easy management of a hotel. It will
be very helpful to the manager on the one hand and to the customers as they would be able to get good
and fast service.

1.3 Scope
In this software, the hotel manager can add new customers and manage that customer
information. Restaurant manager can add restaurant bill in that customer bill. This software works at all
hotels that cater to a large number of customers and want to computerize the complete management
process.

1.4 Objective
The objective of Hotel Management system is to develop a project which maintains booking of
rooms and handles accounts of a hotel. It is a window based application to be implemented in java.

1.5 Definition, Acronyms and Abbreviations

H.M.S. – Hotel Management System

End users – The people who will be actually using the system

SQL – Structural Query Language

1.6 References
Websites:

 https://www.slideshare.net/udaschand940/software-requirementspecification-srs2

Books
  Applying UML and Patterns 2nd Edition Craig Larman
 SE A Practitioner's Approach 7th Edition - Roger Pressman

2. System Requirements Study

2.1 Hardware and Software Requirements

Operating System: Vista, XP, Windows 7 RAM: 512MB or more

2.2 Constraints
2.2.1 Regulatory Policies

All policies relevant to Regulation and this software need to mention here.

2.2.2 Hardware Limitations

When server cannot cater to more number of users, it takes time to process.

2.2.3 Interfaces to Other Applications

There is no interface with other application.

2.2.4 Parallel Operations

Parallel operation for hotel management is to create user and allocating room.

2.2.5 Higher Order Language Requirements

As the program is written in JAVA, server must be available to process the script of JAVA.

2.2.6 Reliability Requirements

The software is of no use if it doesn’t provide reliability.

2.2.7 Criticality of the Application

Attention must be paid to the critics i.e. how to remove the problem and how to add a new
feature.

2.2.8 Safety and Security Consideration

The software should not cause spread of a virus.

2.3 Assumptions and Dependencies

Assumptions made:

The software should work on different operating systems.

There should be database backups.

3. System Analysis

3.1 Study of Current System

Current system for hotel management is fully based on paper work. Hotel Management has to
manage all records of customers and rooms in papers.

3.2 Problem and Weaknesses of Current System

Paperwork is tedious job. There is delay and the problem of human error in allotting rooms and
providing services.

3.3 Requirements of New System

3.3.1 User Requirements

There should be software which allocate rooms automatically and maintain records of
customers and generate bill automatically for customers.

3.3.2 System Requirements

There should be database backup of hotel management system. There should be Java supported
framework for the system. Operating system should be Windows XP or higher version of Windows.

3.4 Feasibility Study

Does the system contribute to the overall objectives of the organization?

Can the system be implemented using the current technology and within the given cost and
schedule constraints?

Can the system be integrated with other system which is already in place?

3.5 Requirements Validation

It is concerned with showing that the requirements actually define the system which the
customer wants.

3.6 Features Of New System

 Easy management of checking –in and other processes.

 Saves time
 Can give accurate information about hotel when required
 Billing becomes easy
 Customer information
 Reduces paper work

Software Requirements
Specifications
FOR

HOTEL MANAGEMENT SYSTEM

Version1.0

Prepared By
M. Usman Haider
&
Zain Tariq

16 Aug, 2020
 Revision History

Version Description Author Date

This will provide

Zain Tariq
Functional and Non-
1.0 16 Aug, 2020
Functional requirements
Muhammad Usman Haider
of the system.
 1. Introduction

1.1 Project Summary

This is software for managing the general activities of a hotel like booking of rooms, billing etc. The
purpose of this document is to collect, analyze and define high-level needs and features of the Hotel
Management System. It focuses on the capabilities needed by the stakeholders, and the target users,
and why these needs exist. The details of how the Hotel Management System fulfills these needs are
detailed in the use-case and supplementary specifications.

1.2 Purpose
This software is aimed at facilitating the prompt, accurate and easy management of a hotel. It will
be very helpful to the manager on the one hand and to the customers as they would be able to get good
and fast service.

1.3 Scope
In this software, the hotel manager can add new customers and manage that customer
information. Restaurant manager can add restaurant bill in that customer bill. This software works at all
hotels that cater to a large number of customers and want to computerize the complete management
process.

1.4 Objective
The objective of Hotel Management system is to develop a project which maintains booking of
rooms and handles accounts of a hotel. It is a window based application to be implemented in java.

1.5 Definition, Acronyms and Abbreviations

H.M.S. – Hotel Management System

SRS – Software Requirements Specification

End users – The people who will be actually using the system

SQL – Structural Query Language

1.6 References
Websites:

 https://www.slideshare.net/udaschand940/software-requirementspecification-srs2

Books
 Applying UML and Patterns 2nd Edition Craig Larman
 SE A Practitioner's Approach 7th Edition - Roger Pressman
 1.7 Overview

This SRS is organized into two parts the first is the overall description and the second
section is the specific requirement.

The overall description will describe the requirement of Hotel Management System. The

specific requirement section describes the detail of the system.

2. Functional Requirements
2.1 Make Reservations

SRS-1 MemberCode, Total childs, Total Adults, check-in date, check out
date, status, Number of nights
SRS-2 Database Record, Database successfully updated pop-up

SRS-3 Validate the given details and record the information in to the
database.

2.2 Add Guest

SRS-4 Member MemberCode, Contact, Company, Name, E-mail,

Gender, Address
SRS-5 Database Record, Database successfully updated pop-up

SRS-6 Validate the given details and record the information in to the
database.

2.3 Add Staff Member

SRS-7 MemberCode, Employee Name, Employee Address, NIC, Salary,

Name Age, Occupation, E-mail

SRS-8 Database Record, Database successfully updated pop-up

SRS-9 Validate the given details and record the information in to the
database.

SRS-10 Period, Check-in, Check-out, Guest

 SRS-11 Display a pop-up with available room details

SRS-12 Validate the given details and check for the available rooms in a
given time period and return its availability.

2.4 Search Room

2.5 Add Payments

SRS-13 Total,1 pay time, Credit card details

SRS-14 Database Record, Database successfully updated pop-up

SRS-15 Validate the given details and record the information in to the
database.

2.6 Issue Bill

SRS-16 Billing no, Quantity, Price, Taxes, Date, Services, Unit

SRS-17 Printed version of the bill

SRS-18 Validate the given details and total cost is calculated according to
the
Services gain by the customer.

2.7 Set Rates

SRS-19 Check-in, Check-out, Day, No. of guests, First night price,

Extension price

SRS-20 Database Record, Database successfully updated pop-up

SRS-21 Validate the given details and record the information in to the
database.

2.8 Taking Backups

 SRS-22 Location to save the backup file

SRS-23 Display a pop-up showing backup successfully created

SRS-24 Validate the user given location to save the backup file. Save the
backup file to the user specified location

3. Non-Functional Requirements

3.1 Availability
The system should be available at all times, meaning the user can access it using
application. In case of a of a hardware failure or database corruption, a replacement
page will be shown. Also in case of a hardware failure or database corruption,
backups of the database should be retrieved from the application data folder and
saved by the administrator. It means 24 x 7 availability.
3.2 Security
The system use SSL (secured socket layer) in all transactions that include any
confidential customer information.
The system must automatically log out all customers after a period of inactivity
3.3 Reliability
As the system provide the right tools for problem solving it is made in such a way
that the system is reliable in its operations and for securing the sensitive details.
4. Performance
The system is interactive and the delays involved are less. When connecting to the
server the delay is based editing on the distance of the 2 systems and the configuration
between them so there is high probability that there will be or not a successful
connection in less than 20 seconds for sake of good communication.

4.1 Resources Required

 Hardware Minimum Recommended
Processor 1 Core 2 GHz Dual Core 2 GHz
Ram 1GB 2GB
Hard-Drive 20GB 80GB

5. Design Constraints
RUP will be used for the design purpose and UML will be used for the diagrams in
MS Visio. C language will be used for the development and for the Database MS Excess
will be used.
6. User Help/Manuals
Detailed system manuals are given to the system users and one week training
session will be held to ensure that the users of the system understands the system fully
and can get the maximum benefit from the system.
7. External Interface Requirements
7.1 User Interface
The user interfaces will be friendly because they will be made after discussions
with the end users. The software will be interactive and self-explanatory.
7.2 Hardware Interface
The system will interact with the printer if the user wants to prints the reports.
7.3 Software Interface

Software Use Version

Windows Operating System Xp,7,8,10
MS Visual Studio Front End 2010 or Newer
MS Excess Backend Latest is Better
MS Visio For Modeling 2010 or Newer

8. Licensing Requirements
This system will be developed according to the business oriented nature of BDS,
and it is licensed by Hotel Management Department.