Software Requirements

Specification
for

Food Gainda
Version 1.0

Prepared by:

 Syed Talha Suleman

 Mustafa Jawed
 Mehak Suraksha
 Raja Izhan Abbasi

Muhammad Ali Jinnah University

 14-3-21

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Contents
1. Introduction.................................................................................................................................1
1.1 Purpose.............................................................................................................................................1
1.2 Intended Audience............................................................................................................................1
1.3 Product Scope...................................................................................................................................1
2. Overall Description.....................................................................................................................2
2.1 Product Perspective...........................................................................................................................2
2.2 Operating Environment.....................................................................................................................2
3. System Features (Functional Requirements)...........................................................................2
4. Other Nonfunctional Requirements..........................................................................................3
4.1 Performance Requirements...............................................................................................................3
4.2 Usability Requirements.....................................................................................................................3
4.3 Security Requirements......................................................................................................................4
5. Deliverables.................................................................................................................................4

`
Software Requirements Specification for Food Gainda Page 1

1. Introduction
1.1 Purpose
The main objective of our module in Food Gainda is to manage the details. Partner
restaurants must register themselves to login into the system administration. The
system admin should also have the web-panel through which they should be able to
Manage restaurant menu, manage acceptable payment methods and Manage client
orders. They will receive a notification whenever they get an order.

1.2 Intended Audience

Our Intended Audience will be the partner restaurant who wish to sell their food
through our app and System Administration who will be overviewing orders, bills, and
smooth delivery of restaurants.

1.3 Product Scope

This Case study looks at the problem of setting up a partner restaurant web panel.
 Our partner restaurants can easily register and login any time.
 Our Partner restaurants will not have access to app, but they will also be provided with web panel.
 In their web panel they can view and manage orders.
 They can edit their menu anytime.
 They can change their payment method.
 They will also receive a notification when an order is placed which will help them manage their
orders.
 They will also be able to view their order details easily.

2. Overall Description
2.1 Product Perspective
Food Gainda is a self-contained, standalone product. Food Gainda is mainly targeted toward pre-established
and new businesses, as the purpose is to integrate into and improve upon local food delivery and make it
easier for the customers and restaurants. It is multiple user’s editable application focusing on a simple user
interface with little to no required technical background. Our web panel is user friendly and is
designed in such a way to make important details easily accessible for the partner
restaurants.

2.2 Operating Environment

 Food Gainda application requires android 4.0 and later.
 Food Gainda application requires IOS 9.0 and later.
Software Requirements Specification for Food Gainda Page 2

 Food Gainda application is built on react native(which is hybrid language and works
with both iOS and android).
 Food Gainda’s web panel will work with Window, Linux and Macintosh.

2.3 System Features (Functional Requirements)

Partner Restaurant Account Creation
 Application supporting multiple users.
 Admin of this system are able to create a personal user account through the User
Account module.
 Admin will set the authorization to each user.
 The created user account stores all authorized information and perform action allowed
to that particular account.

Web panel

 Web panel will be created.

 Partner restaurants will be able to view and manage orders.
 They will be able to edit their menu anytime.
 They will be able to change their payment method.
 They will also receive a notification when an order is placed which will help them manage
their orders.
 They will also be able to view their order details easily.

3. Other Nonfunctional Requirements

3.1 Performance Requirements
 Some of the performances identified are listed below.
 The database will be able to accommodate a large number of records.
 The software will be able to support the use of multiple users at a time.
 Data input and extraction (latency rate) should not be more than a few seconds.
 System will be able to handle the amount of data to be processed within certain time
periods for both normal and peak workload conditions.

3.2 Usability Requirements

 System must authorize the user through username/email and password to perform some
critical operations in the system.
Software Requirements Specification for Food Gainda Page 3

 System shall restrict the user's operation within its user role.
 System used http protocols for secure encrypted communication to the server that prevents
from attackers to get the private data of the user.
 System will able to check data integrity constraints for transactions to be performed

3.3 Security Requirements

All transactions, logged information, updates, user activities are backup at the end of each
day if user wants.

4. Deliverables
The system should be able to provide with available restaurants in the vicinity, updated
menu of each restaurant and a cart for total billing in the end a checkout system
proceeding with a place order hover.