Software Requirement

Specifications
For

Hotel Management System

Version 2.4
Prepared by Minahil Asif
Lahore College For Women University

Date created <1 Aug ,2023>

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..............................................................................2
1.4 Product Scope...............................................................................................................................2
1.5 References....................................................................................................................................3
2. Overall Description..................................................................................................................4
2.1 Product Perspective......................................................................................................................4
2.2 Product Functions.........................................................................................................................4
2.3 User Classes and Characteristics..................................................................................................8
2.4 Operating Environment..............................................................................................................10
2.5 Design and Implementation Constraints.....................................................................................10
2.6 Project Documentation...............................................................................................................11
2.7 User Documentation...................................................................................................................11
2.8 Assumptions and Dependencies.................................................................................................11
3. External Interface Requirements.........................................................................................12
3.1 User Interfaces............................................................................................................................12
3.2 Hardware Interfaces....................................................................................................................17
3.3 Software Interfaces.....................................................................................................................17
3.4 Communications Interfaces........................................................................................................17
4. System Features.....................................................................................................................18
4.1 E-R Diagram...............................................................................................................................18
4.2 Use Case Diagram.....................................................................................................................19
4.3 Use Case Scenarios.....................................................................................................................20
4.5 Activity Diagrams.............................................................................................................................34
5. Other Nonfunctional Requirements.....................................................................................49
5.2 Performance Requirements.........................................................................................................49
5.3 Safety Requirements...................................................................................................................49
5.4 Security Requirements................................................................................................................49
5.5 Software Quality Attributes........................................................................................................50
5.6 Business Rules..............................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5

Revision History
Name Date Reason For Changes Version

1.Introduction
The hotel Management System is a tool for booking the rooms, gernating bills and all day report of hotel.

1.1 Purpose

This hotel management system’s SRS Objective is to provide a base for the foundation of the project.It
gives us a view flow of “How the system works?” And “what are the user expectations?.

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 is 12pt with 1.5 line spacing. It has bold 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.
1.3 Intended Audience and Reading Suggestions
The intended audience of this document would be owner and specific employees like Manager
and Receptionist of Hotel and project team with the objective to refer and analyze the
information.
1.4 Product Scope
The objective of the Hotel Management System is to streamline and automate various hotel operations,
including reservation management, guest check-in/check-out, room allocation, billing, and reporting. 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.

1.5 Reference

”Hotel Management Case Study”, March.6, 2010.

[Online].Available:http://www.scribd.com/doc/27927992/Hotel-Management-Case-Study,
[Accessed: July.28, 2023]Description with UML for a Hotel Reservation System.” Hotel Receptionist
Resume Sample” [Online].Available:http://coverlettersandresume.com/receptionist/resume-sample-
of-hotel-receptionist/, [Accessed: July.23.2023]

2. Overall Description
2.1 Product Perspective

The newly Hotel Management System introduced system that 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.

2.2 Product Functions

 Guest registration and profile management

  Room availability and reservation management
 Check-in and check-out procedures
 Billing and payment processing
 Housekeeping and maintenance management
 Taking backup
 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:

1. Hotel Manager 2. Receptionist 3.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.

Receptionist

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

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 .

2.4 Constraints
  Memory: System will have only 10GB space of data server.
 Language Requirement: Software must be only in English.
 Budget Constraint: Due to limited budget, HMS is intended to very simple .
 Implementation Constraint: Application should be based on C++ only.
 Reliability Requirements: System should sync frequently to backup 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.

3. System Features
3.2 Functional Requirements:

REQ-1.User Registration and Authentication: Requirement: The system shall provide a user
registration mechanism allowing guests to create accounts with a unique username and password.
REQ-2.Room Reservation: Requirement: The system shall allow guests to search for available rooms
based on their preferred dates, room type, and other criteria.
REQ-3.Check-in and Check-out: Requirement: The system shall facilitate the check-in process by
capturing guest information, verifying identity, and assigning room keys.
REQ-4.Room Management: Requirement: The system shall maintain an updated inventory of available
rooms, including their current status (occupied, vacant, reserved).
REQ-5Guest Profile Management: Requirement: The system shall allow staff to create and manage
guest profiles, including personal information and preferences.
REQ-6.Billing and Invoicing:Requirement: The system shall generate itemized bills for guests,
including room charges, additional services, and applicable taxes.
REQ-7.Housekeeping Management: Requirement: The system shall allow staff to view a list of rooms
requiring cleaning and update their cleaning status.
REQ-8.Staff Management Requirement: The system shall enable administrators to create, modify, and
deactivate staff accounts with appropriate roles and permissions.

4. External Interface Requirements

4. 1 User Interface: The system shall have a user-friendly web-based interface for both guests and staff
to access the system. The user interface shall be responsive and compatible with various devices,
including desktops, tablets, and smartphones.
4.2 Hardware Interfaces: The system shall be compatible with various hardware devices, such as card
readers for key access, printers for generating bills, and POS systems for payment processing.
4.3 Software Interfaces: The system shall integrate with external services, such as payment gateways
for online payments, to process transactions securely.
4.4 Communication Protocols: The system shall support standard communication protocols, such as
HTTPS for secure data transmission over the internet. APIs (Application Programming Interfaces) shall
be provided to allow integration with third-party services or mobile applications.

5. Other Non Functional Requirements:

5.1 Performance Requirements: The system shall handle a minimum of 100 concurrent users
without significant performance degradation. Response times for critical operations (e.g., room
reservation, check-in) shall be within 2 seconds.

5.2 Security: The system shall implement industry-standard encryption for sensitive data, including guest
information and payment details. Role-based access control shall be enforced to restrict unauthorized
access to specific features and data.

5.3 Safety Requirements: Backup and Recovery: The system shall perform daily backups of critical data.
Error Handling: The system shall provide clear error messages and gracefully handle unexpected errors
to avoid data corruption or loss.

5.4 Software Quality Attributes: Usability: The user interface shall be intuitive and easy to navigate
Reliability: The system shall have an uptime of at least 99.9% to ensure continuous availability and
reliability. Maintainability: The system's code shall be well-structured and documented to facilitate
future maintenance and updates.

Appendix A: Glossary

Check-out – settle one’s hotel bill before leaving

Check-in – the process whereby a guest announces their arrival at the hotel
Appendix B: Analysis Model
Rivision History

Name Reason for changes Version

Hotel management system Networking ability, emailing 2.0
ability
Hotel management system Add infinity rooms rate ability 2.1
Hotel management system Added child rate calculation 2.2
Booking price adjustment
Import/Export customer details

Hotel management system Added Final Invoice 2.3

Added Invoice Logo selection

Hotel management system Database Backup Facility 2.4

Venue Bookings i.e. Restaurant
Venue Booking Re
Hotel management system ooking Information 2.5
Maintenance Schedule
Room Leave Dates Display

Hotel management system Added Online Booking Ability 2.6

Added payments received
report