Hotel and Restaurant Management

System(HRMS)
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

Iqra Naheed

Document Approval
The following software Requirement Specification has been accepted and approved by the
following:

Supervisor Name Signature Date

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
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
5.3.1.1 Level 1 Artist features Diagram 31

3|Page
 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
Screen Images
9 Supporting Information 46
9.1 Overview of technology 47
9.1 Appendix A-Background Research on: 48

4|Page
 Chapter# 1

Introduction

5|Page
 1. Introduction
This document explains the specifications and requirements of the "Hotel and Restaurant
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 and Restaurant
Management System”.
“Hotel and Restaurant Management System” is an online application which is used to display
and sell food of their nationality, and other narrow consideration through auction.They can host
their food work either for auction or for fixed price. The chef and Manager is liable to pay a
fraction of the price of each customer to the web site to find the running fund for site. Food
lovers have to go to the food exhibition to collect their favorite food.
1.1 Objective
The objectives of developing the MHR are as given below: -
o To store data of the user who are registered in the site.
o To solve the user’s problem in time efficient manner. Helping the user to search
different types of food with a search tools
o To facilitate easy retrieval of data as and when required for enjoyment by the
user.
o Online updating of all type of food updating data using web based interfaces and
with the help of buttons and links in an easy website.
o Developing a viable candidate system that fulfill the Faster and accurate
information retrieval
o Easy registration
o Login dependent information retrieval and updating. Correct and consistent
maintenance of data and its quick retrieval.

This project has more features:

 No data duplication
 Time Efficient
 Cost Efficient
 User friendly environment

6|Page
  Easy performance check
Modules:
 Login
 User Registration
 Food Manu
 Email facility
 Online booking
 Feedback
 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.
 Output device : High Resolution Monitor.

Software Requirements Specification (SRS)

Software Requirements Specification (SRS) is the starting point of the
software developing activity. As system grows more complex it becomes
evident that the goal of the entire system cannot be easily comprehended.
Hence the need for the requirement phase arose. The software project is
initiated by the client needs. The SRS is the means of translating the ideas
7|Page
 of the minds of clients (the input) into a formal document (the output of the
requirement phase).
The SRS phase consist of two basic activities:
Problem/Requirement Analysis:
The process is order and more nebulous of the two, deals with understand the
problem, the goal and constraints.
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 the SRS document is the basic of this phase.
Role of SRS:
1. The purpose of the SRS is to reduce the communication gap between the
clients and the developers.
2. SRS is the medium though which the client and user 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:-

8|Page
• Requirement
• Analysis
• System design
• Implementation
• Testing
• Maintenance

Requirements

Analysis

Design

Implementation

Testing

Maintenance

1.3 Scope
Hotel and Restaurant Management System is a website that displays many food
manues. Usually, the HRMS is run as a business, with the purpose of displaying the food

9|Page
 tastes being to promote it to potential buyers. Other variations include: Hotels for many
people also known as an online secondary hotels.

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.

10 | P a g e
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.
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.

11 | P a g e
 Chapter# 2

The Overall
Description

12 | 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, apache 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 HR Functions
This web project is all about HR, which consists of two views.
 Admin panel
 Client Panel
Where admin is responsible for whole database. Admin can perform all the designs,
creates and update operations. Admin officer responsibilities include processing data
updating company policies and assisting in hiring process.admin responsibilities are:
▪ Organize and maintain personal records.
▪ Update internal database.
▪ Prepare HR docutments,like employment contracts and new hire guide.
▪ Revise company policies.
▪ May update the items in the database

13 | 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 HRMS 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 insert new paintings, 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 user, user can login and upload his
information and also check another profile. The second user is the administrative who
have the capability for maintain the record. Admin manage the whole database. Admin is
the person who will control the application by entering new events, by updating or
deleting new events. I.e. food taste and categories.
2.4 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.
2.5 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.

14 | P a g e
  The mentioned system will use the latest tool available in the market, 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.6 Pricing
▪ By knowing how much and when to drive prices up during high peak period.
▪ Lowering prices to ensure rooms are rented during low peak periods ,hotel can bi
maximize their return.

2.7 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 period;

▪ If the guest is a VIP; or,
▪ You want to capabilities on an event.
▪ You can get even more specific by offering things like mobile only promotion.

15 | P a g e
 Chapter#3

Specific
Requirement

16 | P a g e
3 Specific Requirement
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 HTML5, CSS3, php
and different frameworks and libraries. a JS library and Bootstrap, 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
HTML5, CSS3 and php and different libraries and 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
AWMS 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 Mysqli
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 paintings,

17 | P a g e
Delete artist Update profiles, Update User, and Delete User. Then the following features related
to User are described: Search Paintings, Registration, and feedback, they are followed by a
detailed specification of the functionality of the AWMS. Data definition will also be discus in
this document .Data flow diagram will be provided in these documents.
4.2.1 Add Artist profile
4.2.1.1 Introduction
This functional feature deals with the administrator. The admin can add new painting in the
database by using the interface of the AWMS.
4.2.1.2 Inputs
The admin will enter the Artist name, Artist 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 artist profile
4.2.2.1 Introduction
This functional feature also deals with the administrator. The admin can delete Artist in the
database by using the interface of the AWMS.
4.2.2.2 Inputs
The admin will delete the item in the database with the help of ID of the artist. He would select
the id of the artist 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.
4.2.3 Make a New User

18 | P a g e
4.2.3.1 Introduction
This functional feature too deals with the administrator. The admin can make new admin in the
database by using the interface of the AWMS.
4.2.3.2 Inputs
The admin will enter the name, username, email id and password of the new admin 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 User
4.2.4.1 Introduction
This functional feature also deals with the administrator. The admin can update an existing user
in the database by using the interface of the AWMS.
4.2.4.2 Inputs
The admin would edit the user name, user address and other details about the user 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 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.
4.2.5.2 Inputs
The user will enter his complete name, address, his phone number, email address to register him.
4.2.5.3 Processing

19 | P a g e
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 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 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 describe the high level functions and scope of a system. These diagram 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.

20 | P a g e
 Fig’s Use case Registration

Login

Get profile

Painting Categories

Search by Artist

Order

Payment

21 | P a g e
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.
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,
Uname=Username, Pwd=Password, Fname= First name

22 | P a g e
 ER Diagram

Uname
Pwd
Unamee
Pwd
n

Login Artist

Authentication
Member Artist
Update

Fname Uname Email

City
Profile

ArtID Artist

View Artby Arts

Shipping

Artist Billing
Artpath

Drafts Order
ArtID

Credit Payment

23 | 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 “AWMS”. 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.

24 | P a g e
 Chapter# 4

Analysis Models

25 | 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.

26 | P a g e
 Sequence Diagram

Categories Order

Select the Click the order Button

Painting

Order form
Select the painting
Category
Fill all the
requirement
Click the save
button Order notification
To admin

Approved by admin

Order notification to
artist

27 | 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.

A
Member Artist

Admin

Fig’s DFD

28 | 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.

Member Login Artist

Login A

Register Register

Get
Details Get Details

Admin

Fig’s Context Diagram

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

R
Artist

Login
Database

S U
G V

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

Artist

Member
AWMS Database

Admin

31 | P a g e
4.4 Object Diagram

1:1 A-Admin 1:1

1:1 1:1 1:1

1:*

1:*

1:*

1:*

M-Member L-Login R- T- AWMS

Registratio Transaction
n

32 | P a g e
4.5 Activity Diagram for member

Registration

Input details

Store details

Display details

Login

Valid

Get profile

View AWMS

Add to cart

Password

Payment

33 | P a g e
4.6 Activity Diagram for Artist

Registration

Input details

Store details

Display details

Login

Valid

Get profile

View AWMS

Update AWMS

34 | P a g e
4.7 Sate Chat Diagrams

State Chart Diagram for online registration

User Registr Admin Databas

Registration Store
ation Validation e

Confirmation

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

Login Valid

Purc
hase Store

Registratio Login Transaction

Admin Database
n

Confir
mation

36 | P a g e
 Chapter# 5

Data Design

37 | 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 art_work where some website pages like admin, pages, reach_us, slider,
social_media, user_reg.

38 | P a g e
 2) Admin

Description

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

39 | P a g e
 3) Pages

Description

This table keep record of dashboard, home and about_us.

40 | P a g e
 4) Reach_us

Description

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

5) Slider

41 | P a g e
Description

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

6) Social_Media

42 | P a g e
Description

This table keep record of admin id, Facebook page’s link, twitter’s link and instagram link.

43 | P a g e
 7) User_reg

Description

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

Chapter# 6
44 | P a g e
 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 (CascadingStyle 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.

45 | 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.

46 | P a g e