Srs Document

_______________________
Software Requirements
Specification
for
Online Restaurant Reservation

System
Prepared by:
Abrar Shaikh 2106173

Omkar Shelke 2106176
Rohan Shinde 2106181
Government Polytechnic, Pune
04th September, 2023
1
Table Of Content
1. Introduction……………………………………………………………………………..3
1.1 Purpose……………………………………………………………………………3
1.2 Scope………………………………………………………………………………3
2. Requirement Specifications…………………………………………………………..3
2.1 Functional Requirements……………………………………………………….3
2.2 Non-Functional Requirements………………………………………………….6
3. Safety and Security…………………………………………………………………….7
3.1 Safety Requirements…………………………………………………………….7
3.2 Security Requirements…………………………………………………………..7
3.3 Quality Attributes…………………………………………………………………7
4. System Features………………………………………………………………………7
5. References…………………..………………………………………………………...7
2
1. Introduction
1.1 Purpose
In the proposed ordering system, we provide facility customers to reserve tables for dining,
and can also get details of hall availability for reservation of parties and celebrations. At the
same time this online reservation system will provide the restaurant owner to manage their
services including food. This document includes detailed information about requirements of
the project. It reflects identified constraints and proposed software functionalities, also
specifies functional and nonfunctional requirements.
1.2 Scope
The scope of this application includes reserve table for dining online, also get details of hall
availability for reservation of party and celebrations. At the same time this online reservation
system will provide the restaurant owner to manage their services including food. Currently
proposed system will be fast and easy to use and involves the application of have modules
which are the reservation, the order takeaway, your order gallery and contact us. This
system will manage by two main android applications, first one would be available for
general customers for viewing and booking of table and halls. Second would be used by the
admin to manage the services with in the restaurant premise.
2. Requirements Specification:
2.1 Functional Requirements
2.2 Non-Functional Requirements
2.1 Functional Requirements:

The main function of this application is online table reservation:
1. Table Reservation:
The main function of this application is online table reservation user can reserve any
table through this application anytime and from anywhere.
2. Hall Booking:
The second main function is user can book hall using this app also cancel booking
when they need.
3. Food Ordering:
User also can order their favourite food using this application by just filling the form.
4. Contact Us:
User can contact with hotel admin any time using this application.
3
Use Case
 Log in
 Manage order
 Manage table
 Manage customer
 Manage bookings
 View food
 View Booking
 Reserve table
 Place order
User Classes and Characteristics:

The various users of this app are classified into two types: -
Administrator
Candidate -
Customers
Employees
This app requires the user to have characteristics such as the user should be able to
communicate and write in English and should have previous experience of giving an online
exam. If not, the candidate should be instructed about the basic’s usage of the app by
authorized personnel.
Use case Diagram:
4
Data flow Diagram:
5
Entity Relationship Diagram:
2.2 Non-Functional Requirements:

1. Performance
 Response Time: Specify the maximum acceptable response time for various system
functions.
 Throughput: Define the number of transactions or operations the system should
handle per unit of time.
 Scalability: Describe how the system should scale to accommodate increased load
or user numbers.
 Concurrency: Specify the level of concurrent users or processes the system must
support.
2. Reliability
 Availability: Describe the percentage of time the system should be available for use
(e.g., 99.9% uptime).
 Fault Tolerance: Define how the system should handle failures or errors without
data loss or service disruption.
 Recovery: Specify the time or process required to recover from a failure.
3. Security
6
 Authentication: Define the requirements for user authentication and access control.
 Data Encryption: Specify how sensitive data should be encrypted.
 Audit Trails: Describe the logging and auditing requirements for tracking system
activity.
4. Usability
 User Interface: Define usability guidelines, such as accessibility standards and user-
friendly design.
 Documentation: Specify the availability and comprehensibility of user manuals or
online help.
 Training: Describe any training requirements for end-users or administrators.
5. Compatibility
 Operating Systems: List the supported operating systems and versions.
 Browsers: Specify which web browsers the application should be compatible with.
 Hardware: Define any hardware dependencies or requirements.
3. Safety and Security Requirements

3.1 Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
3.2 Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious access,
use, modification below. Keep specific log or history data sets.
3.3 Software Quality Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly to all the
users.
The software quality attributes are assumed as under:
 Accurate and hence reliable.
 Secured.
 Fast speed.
 Compatibility
4. System Features
Some Performance requirements identified is listed below:

 The database shall be able to accommodate a minimum of 1,000 records of Users.
 The software shall support use of multiple users at a time.
 There are no other specific performance requirements that will affect development.
5. References:
This web application has been prepared based on discussion with Team members and
also taken information from following website – www.google.com , https://www.scribd.com and the
IEEE website.

Srs Document

Uploaded by

Copyright:

Available Formats

Srs Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Srs Document

Uploaded by

Copyright:

Available Formats

_______________________

Online Restaurant Reservation

Abrar Shaikh 2106173

Government Polytechnic, Pune

04th September, 2023

2.2 Non-Functional Requirements

2.1 Functional Requirements:

User Classes and Characteristics:

Use case Diagram:

2.2 Non-Functional Requirements:

3. Safety and Security Requirements

3.2 Security Requirements

3.3 Software Quality Attributes

Some Performance requirements identified is listed below:

You might also like