Food Delivery Android App

1.Problem Statement

1.1problem 1 & Description

1.2 Problem 2 & Description

2.Project Scope (Goal of Project)

3.AS-IS Business Process

3.1 UML Diagram

3.2 Description

4.TO -BE Business Process

4.1 UML Diagram

4.2 Description

5.Functional Requirement

5.1 User Interface Screen 1 & Description

5.2 User Interface Screen 2 & Description

5.3 User Interface Screen 3 & Description

6.Non-Functional Requirement

6.1 UI/UX requirement

6.2 Static Data

6.3 Hardware Configuration

6.4 Software & data License

6.5 Network Requirement

6.6 Hosting Requirement

6.7 Transition Requirement

6.8 Security Requirement

6.9 Performance Requirement

6.10 Third party Integrations

7.Assumptions & Constraint

7.1 Assumption 1

7.2 Constraint 1
Business Requirement Document
Project Name -Food Delivery App
Document History:-
Version Prepared BY Prepared Review By Review Date Change Log
Date
V1.0 Muthurajan 10/02/2023 Omakar 10/02/2023 NA

BRD Template
1.Problem Statement: -
1.1Problem 1 & Description
Different food delivery application often provide different offer or discounts .Users also not
satisfied with their delivery time and random cancellations .Suggestion an app which can
solve these problems and increase user interaction.
The current food delivery applications provide different discounts on the same item but in
different platform .It is also seen that delivery time of an item is not same in all application .
Adding all the discounts and estimated delivery time of different food joints under a single
interface will be economical and less time consuming .
1.2 Problem 2 & Description
The age group of users are mostly 18-40 years .In this age group ,users are mostly busy and
engrossed in their work .so going through all the discounts and price ranges are difficult and
time consuming.
Users prefer to order food during their lunch time which is of a very small duration mostly 40
mins.
Users like to order the food that they are comfortable with. So, a detailed ingredients list is a
plus point, in case the users are prone to allergies of a certain element.
Users also prefer those foods joints which provide faster and smoother delivery.
2.Project Scope (Goal of Project)
The increased utilization of the Online ordering app has allowed restaurants to work
efficiently. They can quickly accept the offer of their customer and provide them with the
estimated time for delivery of food at their doorstep. Such factors help them to build a strong
relationship with their customers. The mobile app offers users the freedom to place orders
from anywhere.
3.AS IS Existing Business
3.1 UML Diagram on High Level (Activity/Flowchart)
3.2 Description
This login and activity and flow of diagram where customer goes to login and sees the order
and make payment add up the address and location with phone number. All the pages see the
payment iniated to food delivery app and delivery person collect from the Restaurant.
4.To BE (Solution /End product) Business Process
4.1 UML Diagram on High Level (Activity /Flow chart )
4.2 Description
Its shows that activity and flow chart editing, adding, updating delivery, update order, add
order and delete order. User will be able to search the product and generate the report,
category, payment.
All objects like food, order, payment, Interlinked.
Its shows the full description of all the category.
5.Functional Requirements
5.1 User Interface Screen 1 & Description
Functional requirements are certain characteristics or capabilities that a system must have in
order to function properly.
The following are some functional criteria for a food ordering system:

Customers should be able to view the status of their orders, including when they were placed,
when they are expected to be ready, and when they have been delivered (if applicable).

5.2 User Interface screen & Description

Order modification: Customers should be allowed to make changes to their orders until they
are ready for preparation by the kitchen.

5.3 User Interface screen 3 & Description

Customers should be able to choose goods from the menu and add them to their order, as well
as express any special instructions or alterations.

6.Non-Functional Requirement
6.1 UI/UX Requirement
6.2 Static Data
Product Information -Name, Required Storage Container, Packaging Material
Operation Information- Mobile Number, Address and Location and Food order

6.3 Hardware Configuration

A website or app that allows customers to view the menu and place an order, and an admin
interface that enables the restaurant to receive and fulfil customer orders.
No extra Hardware interface is needed
The system will use the standard hardware and data communication sources
This includes general web hosting, server, network, network management tools.
6.4 Software & Data base license
Operating system: Windows 10, Linux
Web browser: the system is web-based application like opera, fire fox and Chrome
6.5 Network Requirement
HTTP protocol for communication with web browser and web server TCP/IP network protocol
with HTTP
6.6 Hosting Requirement
 Ensure Reasonable Bandwidth.
  A Host Should Provide at Least 99.9% Uptime.
 Ensure There's a Backup Plan.
 Look for Strong Security Features.
 The Best Web Hosts Offer 24/7 Customer Support.

6.7 Transition Requirement

 Data conversions
 Temporary interfaces

6.8 Security Requirement

security services that need to be achieved by the system under inspection. Examples could be
authentication, authorization, backup, server-clustering, etc. This requirement artifact can be
derived from best practices, policies, and regulations.
6.9 Performance Requirement
 Response Time
 Workload:
 Scalability:
 Platform:
6.10 Third party Intergrations
 Toast Delivery Services.
 Uber Eats.
 ChowNow.
 GrubHub.
 DoorDash.
 Otter Order Manager.
 Olo.
 Delivery.com.