Mughal e Azam Hotel and Restaurant

Management System (MHRMS)

Software Requirement
Specification
(SRS)

Department of computer Sciences, ASPIRE College

Liaquatpur

Affiliated with the Islamia University of

Bahawalpur
Revision History

Candidate Name Roll No Date

Skeena Bibi 201501

Iqra Naheed 201502

Document Approval
The following software Requirement Specification has been
accepted and approved by the following:
Supervisor Name Signature Date
Mam Mehnaz
Shoukat
Iqra Naheed student of MCs (Session 2020-2022)
Aspire College Liaquat Pur

1|Page
 IN THE NAME OF ALLAH

THE MOST BENIFICIENT

THE MERCIFUL

2|Page
 Table of Contents
Sr# Chapter Page
1 Introduction 6
1.1 Objective 6
1.2 Purpose 7
1.3 Scope 11
1.4 Definitions, Acronyms, and Abbreviations 11
1.5 Reference
1.6 Overview 12
2 The overall Description 14
2.1 Event Perspective 14
2.2 AWMS Function 14
2.3 User Characteristics 15
2.4 General Constraints 15
2.5 Assumption and Dependencies 15
3 System Overview
4 Specific Requirements 18
4.1 External Interface requirement 18
4.1.1 User interface 18
4.1.2 Client Interfaces 18
4.1.3 Administrator interface 18
4.1.4 Software interface 18
4.2 Functional Requirement 18
4.2.1 Add Artist profile 19
4.2.2 Delete Artist Profile 19
4.2.3 Make a new User 19
4.2.4 Update Existing User 20
4.2.5 New User Registration 20
4.2.6 User Login 21
3|Page
 4.3 Use Cases 21
4.4 Classes? Objects
4.5 Non-functional Requirement 23
4.4.1 Performance 23
4.4.2 Reliability 23
4.4.3 Supportability 23
4.4.4 Availability 23
4.4.5 Security 23
4.6 Logical Database Requirements 23
4.6.1 ER Diagram 23
4.7 Design Constraints 25
5 Analysis Models 27
5.1 Sequence Diagrams 27
5.2 Data flow Diagrams(DFD) 29
5.3 Context Diagram 30
5.3.1 Level Diagrams 31
Level 1 Artist features Diagram 31
5.3.1.1
5.3.1.2 Level 2 Admin features Diagram 32
5.4 Object Diagram 33
5.5 Activity Diagram for Member 34
5.6 Activity Diagram for Artist 35
5.7 State Chart Diagram 36
5.7.1 State Chart Diagram for Transaction 37
6 System Architecture
7 Database Design 39
7.1 Tables of Database 39
8 Human Interface Design
Overview of Interface
4|Page
 Screen Images
9 Supporting Information 46
9.1 Overview of technology 47
9.1 Appendix A-Background Research on: 48

5|Page
 Chapter# 1

Introduction

6|Page
 1. Introduction
This document explains the specifications and requirements of the " Hotel Management
website. It describes the functional and Non-functional requirements of the site such as
interface, design and detailed related to "Food Management. This specification document is
intended for the entrepreneurs who are interested open their “Hotel Management System”. The
Hotel Management is a tool for booking the rooms of hotel through online by customer. It
provides the proper management tools and easy access to the customer information.

1.1 Purpose
The Hotel Management system main objective is to provide abase 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 user. Client expectation and requirement s are analyzed to produce
specific unambiguous functional and nonfunctional requirements, so they can be used by
the development team with clear understanding to build a system as per end user needs.
The SRS for HMS can also be used for future as basis for detailed understanding on how project
was started.

1.2 Scope of project

The HMS project is intended for the reservations for room that can be made through online. It
will be able to automate the various operations of Hotel. Our Hotel Management system will
have three end users: Customer, receptionist, and Hotel Manager .Hotel Management system
will consists of Booking Management system DBMS Server. Customer will 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 be able to view the financial report and able to
update room information such as cost and category.

7|Page
This project has more features:
 Easy menu set up
 Sales managing
 Technical support
 User friendly environment
 God quality food
 Skills management
Modules:
 Login
 User Registration
 Check for the availability of Rooms
 Display the Rate
 Conform Room Booking
 Email facility
 Payment of Rooms
 Online booking
 Contacts Us
HARDWARE AND SOFTWARE SPECIFICATIONS SOFTWARE REQUIREMENTS:
 Operating System : Windows 07 2000.
 Language : HTML, Php,CSS
 Technologies : MS Word
 Data Bases : My SQLi
 Server : Xampp
HARDWARE REQUIREMENTS:
 Processor : Any Processor above 500 MHz
 Ram : 4GB
 Hard Disk : 32GB.
 Compact Disk : 10GB
 Input device : Standard Keyboard and Mouse.

8|Page
  Output device : High Resolution Monitor.
1.3 Software Requirements Specification
A Software requirement specification RS is a document that describe what the software will
do and how it will be expected to perform. It also describe the functionality the product
needs to fulfill all stakeholders needs. This Hotel Management gives a comprehensive
view of how the system is supposed to work and what is to expected by the end users.

1.4 Requirement Specification:

Here, the focus is on specifying what has been found giving analysis such as representation,
Specification languages and tools, and checking the specifications are addressed during this
Activity. The requirement phase terminates with the production of the validate SRS document.
Producing of SRS is the phase of document.
Role of SRS:
1. The purpose of the SRS is to reduce the communication gap between the manager and
the customer.
2. SRS is the medium though which manager and customer needs are accurately specified.
3. It forms the basis of software development.
4. A good SRS should satisfy all the parties involved in the system.
Analysis Model
 The model that is basically being followed is the WATER FALL MODEL, which states
that the phases are organized in a linear order. First of all the feasibility study is done.
Once that part is over the requirement analysis and project planning begins. If system
exists one and modification and addition of new module is needed, analysis of present
system can be used as basic model.
 The design starts after the requirement analysis is complete and the coding begins after
the design is complete. Once the programming is completed, the testing is done.
In this model the sequence of activities performed in a software development project are:-
• Requirement
• Analysis
• System design

9|Page
• Implementation
• Testing
• Maintenance

Requirements

Analysis

Design

Implementation

Testing

Maintenance

1.3 Scope
Hotel Management System (HMS) a website that displays many food menus. Usually,
the HMS is run as a business, with the purpose of displaying the food tastes being to
promote it to potential buyers. Other variations include: Hotels for many people also
known as an online secondary hotels. The software to be developed deals with
creating a Hotel Management system which will automate the major hotel
operations such as billing and keeping track of records of daily transition.

10 | P a g e
1.4 Definitions, acronyms and Abbreviations
Web Applications
A type of software that runs on some server. It is usually a piece of software that runs
online.

MySQLi

Database Management System for Managing Database. It Is Also Open Source Software.

Xampp

Xampp is combination of apache php and MySQL database

Server

Server is a powerful system that hosts some web Application.

Open source

A software that is freely available in the city to download its codes for research or
modifications.

Web browser

Software to surf the web

Insertion

A process to insert new records in the database.

Updating

A process to update the existing records.

Deletion
A process to remove some record from the database.

Selection
A process to select a data from database and to show the user.

11 | P a g e
 Admin
A user who manages the whole website at the backend. He is the most powerful user of
the application. He is responsible for the whole database. He can insert, update and
delete data from database.
Client
A user who uses the application from the front end. It can send the request to the server.
Database
A database is the collection of related data that is stored in an efficient and compact
manner. Data is stored in the form of tables in the database. Table is a collection of rows
and columns.
RAM
Random Access Memory, a type of memory. It is a temporary memory.
References
IEEE STD 830-1998, IEEE recommended practice for software requirement
specification.
1.5 Overview
The remaining SRS contains The Overall Description Gallery Perspective
Gallery Functions User Characteristics General Constraints
Assumption and Dependencies.

12 | P a g e
 C

Chapter 2
The overall description

13 | P a g e
 2 The Overall Description
2.1 Event Perspective
As mentioned above, this website is totally independent and not a part of some existing
system. This website needs a server i.e. web server or a local server in our case. The
client send request to the server, the application host on some server will communicate to
the application and to the database management system if needed to facilitate the request.
The database server wills responses user according to demands of the user.

Client Database

Internet
Server
Files

2.2 HMS Functions

This web project is all about HR, which consists of two views.
 Manager panel
 Client Panel
Where manager is responsible for whole database. A manager can perform all update
operations. Manager Officer Responsibilities include processing data updating company
policies and assisting in hiring process.adminresponsibilities are:
▪ Organize and maintain personal records.
▪ Update internal database.
▪ Prepare HR documents, like employment contracts and new hire guide.
▪ Revise company policies.
▪ May update the items in the database

14 | P a g e
 ▪ May delete the items in the database
A client who will use the application from front end, it will be able to visit the website.
Client will be able to select different types of paintings i.e. according to their interest.The
client will be able to search different types of food and different room design with name
HMS should embed the following features and function to its users, i.e. admin and
client.
 Should make the admin able to login into the admin panel after authentication.
 Should make the admin able to build new rooms, new profile and new categories.
 Should make the admin able to view the entire available system in the database.
 Should make the client able to select more than one.
 Should make the admin able to view list all clients.
 Should make the admin able to make new admin, delete or update the existing
user.
 Should provide the security for the system.
2.3 User Characteristics
There are two types of system users. The first is Hotel Manager who can manage all hotel
facilities such as rooms detail rooms booking and guest cares. The second user is Receptionist
will have only access modify all rooms booking detail. The third user is Customer who visits all
rooms during the booking of rooms’ check all facilities of rooms select any one room and pay
the bill of selected room.

2.6 General Constraints

Web application is based on internet which required both hardware and software, so we will
facilitate the requirements about software which are given below. Web application are used the
specific software that are include PHP 6.0 ,Apache and data Base scheme used Mysql and
hardware requirements are dual core process with at least 1GB RAM for used this software. For
better results better hardware will be consider a plus point.

15 | P a g e
2.7 Assumptions and Dependencies

There are some number of factors that are consider to be fulfill to make the project work
according to the requirements described in document.

 The mentioned system will use the latest tool available in the city so it is assumed
the user will use the latest web browser for working that is load the UI properly.
 There is huge involvement of php code so it is assumed that the user will not
disable the php in the browser to run the website smoothly.
 It is assumed that the front-end user is specifically from Pakistan.
 System date corresponds to Actual date and Time.

2.9 Packages and promotions

Packages are any rate that pairs the accommodation with an on; it could be free breakfast
free parking, or even airline ticket.

Promotions are special rates that can change depending on:

▪ The season or holiday periods;

▪ If the guest is VIP; or
▪ You want to capillaries on an event.

16 | P a g e
17 | P a g e
 Chapter#3

Specific
Requirement

18 | P a g e
3 Specific Requirements
4.1 External Interface Requirements
4.1.1 User interface
There are two types of user interface.
1) Client User Interface
2) Administrator User Interface
4.1.2 Client interface
The minimal requirements are that the user would be able to communicate to the system
using GUI. GUI stand for graphical User Interface.GUI is bases on HTML, CSS, php and
different frameworks and libraries. , a CSS framework. Different GUI based component are
used for the following actions.
4.1.3 Administrator Interface
The minimal requirements required for the administrator interface that the admin will
access the control panel through a GUI using some web browser. The GUI again bases on
HTML, CSS andphp and different frameworks. No command line utility will be given to
the user to access the system. Hyperlinks and buttons will be provided to the admin to
perform different tasks.
Hardware Interfaces
HRMS is a Web site that is why all hardware interface of this, will be those of server On
top of which it will be running. Hence the website will incorporate the server for all the
hardware instances such as CPU, memory and communication.
4.1.4 Software interface
As our mentioned system runs on a server, so a server having the capabilities to run the scripts
written in PHP language is required. Moreover the server should have the database like MySQL
in order to make the application able to make transactions with records in database.
4.2 Functional Requirements
This section narrates the features and process performed by the web site. Firstly, the following
features of the system and their interaction with administrator are described check food taste,
delete different food type which has no good taste, select good chief. Then the following

19 | P a g e
features related to manager performance are described: Search different taste of food,
Registration, and feedback, they are followed by a detailed specification of the functionality of
the HMS. Data definition will also be discus in this document .Data flow diagram will be
provided in these documents.
4.2.1 Add HOTEL Manager profile
4.2.1.1 Introduction
This functional feature deals with the administrator. The admin can add new customer in the
database by using the interface of the HRMS.
4.2.1.2 Inputs
The admin will enter the customer name, customer chief address, time, date and other details
about profile using different UI elements.
4.2.1.3 Processing
The server with communicate the MySQL to insert the new item in the database.
4.2.1.4 Outputs
A success message will be shown to the user and database will be updated.
4.2.1.5 Error Handling
An error message will be shown upon some error while updating the item in the database.
4.2.2 Delete manager profile
4.2.2.1 Introduction
This functional feature also deals with the administrator. The admin can delete chief/customer in
the database by using the interface of the HRMS.
4.2.2.2 Inputs
The manager will delete the item in the database with the help of ID of the customer. He would
select the id of the chief/customer from a dropdown menu.
4.2.2.3 Processing
The server with communicate the MySQLi to delete the item in the database.
4.2.2.4 Outputs
A success message will be shown to the user and database will be updated.
4.2.2.5 Error Handling
An error message will be shown upon some error while deleting the item in the database.

20 | P a g e
4.2.3 Make a New User
4.2.3.1 Introduction
This functional feature will be used by hotel manager. The manger can manage a newuserin the
database by using the interface of the HMS.
4.2.3.2 Inputs
The manager will enter the name, username, email id and password of the new manager as input.
4.2.3.3 Processing
The server with communicate the MySQLi to insert the new item in the database.
4.2.3.4 Outputs
A success message will be shown to the admin and database will be updated with a new record.
4.2.3.5 Error Handling
An error message will be shown upon some error while inserting the new user in the database.
4.2.4 Update Existing Customer
4.2.4.1 Introduction
This functional feature will be used by manager. The manager can update an existing user in the
database by using the interface of the HRMS.
4.2.4.2 Inputs
The admin would edit the user/chief name, user/chief address and other details about the
user/chief using different UI.
4.2.4.3 Processing
The server with communicate the MySQLi to update the item in the database.
4.2.4.4 Outputs
A success message will be shown to the user and database will be updated.
4.2.4.5 Error Handling
An error message will be shown upon some error while updating the admin in the database.
4.2.5 New User/chief Registration
4.2.5.1 Introduction
This functional feature deals with the user who is using the application’s front-end. He would
have to register him before any detail.

21 | P a g e
4.2.5.2 Inputs
The user/chief will enter his complete name, address, his phone number, email address to register
him.
4.2.5.3 Processing
The server with communicate the MySQLi to and the user will be added to the database.
4.2.5.4 Outputs
Database will be updated with a new user/chief and a success message will.
4.2.5.5 Error Handling
An error message will be shown upon some error while searching a specific item the database.
4.2.6 User/chief Login:
4.2.6.1 Introduction:
The user may login to artist detail by using the credentials assigned to him upon registration.
4.2.6.2 Inputs
The user will enter his email address and password to login.
4.2.6.3 Processing
The application will communicate to the database to check if the user has registered already.
4.2.6.4 Outputs
User will be logged in if the entered credentials meets the one in the database and a success
message will be shown otherwise he will be asked to enter correct data.
4.2.6.5 Error Handling
An error message will be shown upon some error while logging into the database.
4.3 Use case Diagram
Use case describes the high level functions and scope of a system. These diagrams also identify
the interactions between the system and actors. The use and actors in use case diagram describe
what the system does and how the actors use it but not how the system operates internally.

Fig’s Use case Registration

Search
Rooms
Get by customer
Payment
Login
profile
Categories
Order

22 | P a g e
 Manager

Customer

4.4 Non-functional Requirement

4.4.1 Performance
i. Average load time of the start page of website should be less than 5 seconds.
ii. Average response time of the system should be less than 10 seconds.

23 | P a g e
 iii. Our system should easily accessible on the system having minimum internet speed of
1MB/s.
4.4.2 Reliability
There will be a maximum of 1 bug/KLOC.
4.4.3 Supportability
All code will be written as specified by the Hungarian Naming Convention.
4.4.4 Availability
Seminar Generator will be available to client 7 days a week and 24 hours a day. In case of any
system crash a backup will be available to make the system live.
4.4.5 Security
Users’ information will be secure and he will be able to access only their own personal
information.
4.5 Logical Database Requirements
A logical database must be able to access the identify all files within the storage system to
operate correctly , whereas a physical database manage a much smaller fields of information
sometimes , a physical database stores only a single file with one value or word in it.
4.5.1 ER Diagram
An entity relationship diagrams is essential for modeling the data store in a database. It is the
basic design upon which a database is build. ER diagrams specify what data we will store, the
entities and their attributes.
Note:
Here,
Name=Username, PW=Password, Name= First name

24 | P a g e
 ER Diagram
# ID
Pw
Address

Login
Has PW

Name
#ID

Manager
Name

Pay cus ID #Pay ID

# ID

Customer Manage Payment

Email
Mob. No # ID
Pay amt

Pay date
Address Hotel

Has
Rent
Type

Booking Name
Booking
Name

Book discs
Book type

25 | P a g e
4.6 Design Constraints
Design constraints are limitations on a design. These include imposed limitations that you don’t
control and limitations that self-imposed as a way to improve a design.
4.6.1 Parent component
There is no parent of “HMS”. It works its own.
4.6.2 Application Language
Language used for this application is mainly “PHP” for server side logics and HTML.CSS for
front-end side.4. Analysis Models.

26 | P a g e
 Chapter# 5

Analysis Models

27 | P a g e
4. Analysis Models
List all analysis models used in developing specific requirements previously given in this SRS.
Each model should include an introduction and a narrative description. Furthermore, each model
should be traceable the SRS’s requirements.
4.1 Sequence Diagram
A sequence diagram or system sequence diagram shows objects interactions arranged in time
sequence in the fields of software engineering, it depicts the objects involved in the scenario and
the sequence of the messages exchanged between the objects needed to carry out the
functionality of scenario.

28 | P a g e
 Sequence Diagram

Categories Order

Select the Room Click the order Button

Order form
Select the Room
Category
Fill all the
requirement
Click the save
button Order notification
To manager

Approved by Manager

Order notification to
customer

29 | P a g e
 4.2 Data flow Diagrams (DFD)
A DFD is a way of representing a flow of data through a process or a system. The DFD also
provides information about the outputs and inputs of each entity and the process itself. A data
flow diagram has no control flow there are no decision rules and loops.

Booking Management

Customer Management Room Management

HMS

Hotel Management Login Management

Registration Management

Fig:DFD

30 | P a g e
4.3 Context Diagram
A system context diagram in engineering is a diagram that defines the boundary between the
system, or part of a system and its environment showing the entities that interact with it. This
diagram is a high level view of a system.

Manager Login USER

Login HMS

Register Register
HMS
Get
Details Get Details

Fig’s Context Diagram

31 | P a g e
4.3.1 Level Diagram
4.3.1.1 Level 1 Artist Features Diagram

USER
Registration

Change-
Login Password
Database

Upload
Search By
Get- View-
USER Hotel
profile HMS
Facility

32 | P a g e
4.3.1.2 level 2 Admin Features Diagram

User

Member
HMS Database

Manager

33 | P a g e
4.4 Object Diagram

1:1 Manager 1:1

1:1 1:1 1:1

1:*

1:*

1:*

1:*

M-Member L-Login R- T- HMS

Registratio Transaction
n

34 | P a g e
4.5 Activity Diagram for member

Registration

Input details

Store details

Display details

Login

Valid

Get profile

View HMS

Password

Payment

35 | P a g e
4.6 Activity Diagram for USER

Registration

Input details

Store details

Display details

Login

Valid

Get profile

View HMS

Update HMS

36 | P a g e
 4.7 Sate Chat Diagram

State Chart Diagram for online registration

User Registr Manag Databas

Registration Store
ation Validation er e

Confirmation

37 | P a g e
4.7.1 State chart diagram for online transaction

Login Valid

Purc
hase Store

Registratio Transaction
Login
n Database
Admin

Confir
mation

38 | P a g e
 Chapter# 5

Data Design

39 | P a g e
5. Data Design
5.1 Tables of Database
 Open The Browser and put inside
http://localhost/artwork/
1) Art_work

Description

This website about artwork where some website pages like admin, pages, reach us, slider, social
media, user_reg.

40 | P a g e
 2) Admin

Description

This Table keeps record of admin (like, id, Full name, Username, password)

41 | P a g e
 3) Pages

Description

This table keep record of dashboard, home and about us.

42 | P a g e
 4) Reach us

Description

This table keep record of admin address, city, state, zip code and contact number.

43 | P a g e
 5) Slider

Description

This table keeps record of art image id, image name and path.

44 | P a g e
 6) Social_Media

Description

This table keeps record of admin id, Facebook page’s link, twitter’s link and Instagram link.

45 | P a g e
 7) User_reg

Description

These tables keep record of user first name, last name, gender, contact number, email, password
and address.

46 | P a g e
Chapter# 6
 Supporting

6. Supporting Information

6.1 Overview of the Technology

Front end: HTML, CSS
 Html is used to create and save web document (For example, Notepad/ Notepad++).
 CSS (Cascading Style Sheets) create attractive layout.
Back end: PHP, MySQL
 PHP: Hypertext preprocessor (PHP) is a Technology that allows software developers to
create dynamically generated web pages in HTML, or other document types as per client
request. PHP is open source software.

47 | P a g e
  MySQL: MySQL is a Database, widely used for accessing querying, updating and
managing data in Databases.
Software Requirement
 XAMPP Server

6.2 Appendix A
Glossary
 Actor
It represents a role, external entity that interacts with our system.
 Use case
Graphical Represent of interaction among system and actor.
 Scenario
The time of actual input and expected output.
 Use case diagram
Represent use the services and functionality by the system by the actor.
 Use case Realization
How the use case realizes in the design table model.
 Activity diagram
Graphical represent of the process flow of use case etc.
 Sequence diagram
Represents the interaction of an object to perform a job.
 Collaboration diagram
Alternative representation of sequence diagram.
 Data model
Represent the persistence object model.

48 | P a g e