Sie sind auf Seite 1von 27

Requirements Document

Food Delivery Company

Scope of Work
Version 1.0
21st November, 2019

Drafted by
Talha Pervaiz

Last Modified: 11/25/2019 Page 1 of 27


Requirements Document

Food Delivery System

Table of Contents

1 INTRODUCTION..........................................................................4

1.1 Overview..............................................................................................4

1.2 Abstarct................................................................................................4

1.3 The define of existing problem...........................................................4

1.4 Project Summary................................................................................5

1.5 Platforms Frameworks & Libraries..................................................6

1.6 Project Deliverables............................................................................7

1.7 Compatibility.......................................................................................7

2 END USER MOBILE APPLICATION............................................8

2.1 Overview..............................................................................................8

2.2 Modules................................................................................................8

2.3 Splash...................................................................................................9

2.4 User Registration................................................................................9

2.5 Sign in.................................................................................................10

2.6 Drawer...............................................................................................10

2.7 Home Screen......................................................................................10

2.8 Filters..................................................................................................11

2.9 Work Flow.........................................................................................11

Last Modified: 11/25/2019 Page 2 of 27


Requirements Document

2.10 Cart.....................................................................................................12

2.11 Online Payment.................................................................................12

2.12 Feedback............................................................................................12

2.13 Ratings...............................................................................................12

3 RESTAURANTS REGISTRATION.............................................13

3.1 Overview............................................................................................13

3.2 Modules..............................................................................................13

3.3 Restaurants Registration Form.......................................................14

3.4 Work Flow.........................................................................................14

3.5 Add Meal............................................................................................15

3.6 Category.............................................................................................15

3.7 Orders................................................................................................15

3.8 Reports...............................................................................................16

3.9 Rider Interface..................................................................................17

4 SUPER ADMIN INTERFACE......................................................17

4.1 Overview............................................................................................17

4.2 Restaurants........................................................................................17

4.3 Account approval..............................................................................17

4.4 Orders................................................................................................17

4.5 Payments.............................................................................................18

Last Modified: 11/25/2019 Page 3 of 27


Requirements Document

1 Introduction
1.1 Overview

This document contains information which is confidential to employees


and is submitted to employees on the basis that it must not be used in any
way nor disclosed to any other party, either whole or in part. The only
exception to this is that the information may be disclosed to employees or
professional advisors & clients where such disclosure is on a need to know
basis. This document defines the requirements for the food delivery
system. This document is designed to be beneficial for both the client &
the development team. From this document, the stakeholders will be able
to determine our understanding of the requirements and verify their
accuracy. The development team will be able to use it while developing the
software system to ensure that the customer receives the expected product.

1.2 Abstract

With the increasing popularity of the food delivery system, traditional


telephone order food has inconvenience to the customers and the food
delivery store. How to make the food-delivery more quickly and
conveniently has become a concern of many people. The food-delivery app
has easy and simple features, but now the food-delivery app is no more
convenient for students, working staff & old aged peoples the overall is
relatively old, not novel enough, cannot attract new users. Based on this
feature, we decided to design a system for both the restaurants and the user.
The food-delivery system should be timely, convenient and comprehensive,
many food-delivery systems today, but the function is not comprehensive,
and some did not meet the requirements of timely delivery.

Last Modified: 11/25/2019 Page 4 of 27


Requirements Document

1.3 The define of the existing problem

Now days all across the world, the most common phenomenon is that owing
to the variable timetable of people from all paths of life, it could be more
difficult to decide when and where to have their lunch in a hectic schedule.
The data demonstrate that in New York, three of the top 10 universities have
a good showing when examination almost coming, and like the University of
Virginia has increased 25 percent order spike in the finals NO.8 date
(Svokos, 2015). Thus, many online foods delivering requirements derive
students take consider the quality of delivering food, timeliness,
maneuverability and relative accuracy. To solve this problem, we are going
to develop a system, which is designed mainly for restaurant owners and for
the customer , where restaurant owners can register their restaurant and start
uploading their meals and deals by selecting the suitable package offer by
food delivery company as well customer will be able to select the restaurant
and see the meal offered by the restaurant and order from their favorites
restaurants.
In the existing system for giving any orders, users need to visit hotels or
restaurants to know about food items and they give orders and pay advance.
In this method time and manual work is required. Maintaining critical
information in the files and manuals is full of risk and a tedious process.

1.4 Project Summary

This Food Delivery system enables both restaurant owners and end-users.
End users will have the provision to register online, select the restaurants
from the nearby location, food from the e-menu card, read the E-menu card
and pay online for their order food online, end-users will be able to see their
order status as well as the track their rider. By just ordering the food that the
user wants to have. The results after selecting the food from the E-menu card
will directly appear in restaurant systems, the chef who is going to cook the
food for you. By using this application the work of the Waiter is reduced and
we can also say that the work is nullified. Restaurants Owners will have the
provision to registers their restaurant on food delivery systems by selecting
suitable packages & pay for it. Once restaurant profile gets approved it will
be live for all the users & restaurant will be able to upload their food and
their details and prices restaurants owners will have the provision to assign
an order to riders & riders will be able to get direction for the location from
the live map and rate the customer.
Last Modified: 11/25/2019 Page 5 of 27
Application Technology Platform:
Requirements Document

1.5 Platforms Frameworks & Libraries

For Web Application, Website and Admin Console


1. PHP 7.2
2. Laravel 5.8
3. Mongo DB
4. HTML, CSS

For Mobile Application


1. iOS -- Swift
2. Android

Last Modified: 11/25/2019 Page 6 of 27


Requirements Document

1.6 Project Deliverables

Project
S. No. Details
Deliverables
Detailed  Requirement Specification
1.
Requirements  App Design, UI & UX

 Source code
2. Admin Panel
 Login Credentials

Application  iPhone Application Package to client


3.
Package  Apk file for Android device
 App Package to be submitted to Apple’s
iTunes store
3. Apps publishing
 Android App to be published on Google
Play
4. Application  Source Code

1.7 Compatibility

The food delivery system will be compatible with all mobile devices &
browsers.

o iPhone devices.
o Android phone devices.
o All browsers safari, chrome, Firefox, IE and Edge, etc.
o Mac and Windows
o All screens and resolutions. Starting from
o 768 PX – 1024 (iPhone and Android devices)
o 1024 PX – 1168 PX (iPad/ tablets Landscape)
o 1200 PX – 1280 PX – 1366 PX (Laptop Screens)
o 1600 PX – 1920 PX – 2520 PX (Monitor and big screens)

Last Modified: 11/25/2019 Page 7 of 27


Requirements Document

2 End-User Mobile Application


2.1 Overview

The end-user mobile application will be developed for those who want to
order food online while sitting in their rooms, offices, and students on their
hostel. This food delivery app has full-fleshed functionalities of the online
food ordering system as well as user will be able to pay online for the food
& the user can also track the riders and he will be able to get an update for
their order status.

2.2 Modules

This section will describe the module for the mobile application, the
following will be the main modules.

o Splash
o User Registration
o Sign in
o Restaurants
o Drawer
 My Orders
 My Profile
 Help center
 Invite Friends
 Terms& Condition/Privacy Policy
 Logout
o Rating
o Reviews

Last Modified: 11/25/2019 Page 8 of 27


Requirements Document

2.3 Flow Chart

Last Modified: 11/25/2019 Page 9 of 27


Requirements Document

Last Modified: 11/25/2019 Page 10 of 27


Requirements Document

2.4 Splash

The application shall start with an appealing and interactive splash screen,
which shall display the app’s name and logo. The splash screen’s concept is
that it covers the time while the app is loading and it shows the company
logo in order to promote the app. Different options of the splash screen shall
be provided to the client and final selection shall be the upon client’s
discretion.

2.5 User Registration

The users will initially signup with the app in order to access all of its
components. However, on the first screen user would have the following
steps at his disposal
The app will offer two modes of sign up for the users. Below mentioned are
both the sign-up methods.

Conventional Sign Up

If the user wishes to sign up via the conventional method, he would have to
input the following information in the relevant fields. Moreover, the email
address will be used as a unique identity.

o First name
o Last name
o Email Address
o Mobile number
o Password
Accept term and conditions and privacy policy

Sign up via Social Media

We will incorporate the connect API to execute this feature on Facebook,


and Google fabric API. This feature will essentially allow users to instantly
sign up with the app inputting their Facebook or Google credentials.
Once the user selects a social media platform to sign up with, the app would
redirect them to the respective platforms to ask for authorization.

Last Modified: 11/25/2019 Page 11 of 27


Requirements Document

2.6 Sign in

Login
Using his/her email address and password
Remember Me
If the user doesn’t want to input login credentials every time when login.
Forgot Password
In case the user forgot the password
The user will have to provide the email address from which he’s registered
to the application & and the application will automatically send six-digit
code to the user email address by entering this verification code user will be
able to create his new password.

2.7 Drawer
The drawer will have the following options available for the user assistance.

o My Orders
o My Profile
o Help center
o Invite Friends
o Terms& Condition/Privacy Policy
o Logout

2.8 Home Screen

In-home screen users will have the provision to search for the restaurant or
see the available restaurants in-home screens. Users will be able to see the
restaurants following details added from the backend.

o Restaurants Images
o Estimated delivery time
o Free Delivery or delivery cost
o Minimum order price
o Status
o Location
o Reviews & ratings

Last Modified: 11/25/2019 Page 12 of 27


Requirements Document

As the user selects the restaurant's user can see the e-menu card added from
backend.

2.9 Filters

The user will have the provision to filter out a restaurant based on his
preferences, the following will be options available for the search filters.

o Price
 Seek bar will be available to define the price
o Offers
 Free Delivery
 Deal
 Online payment available
 Cash on delivery
o Cuisines
 Food category

2.10 Work Flow

Last Modified: 11/25/2019 Page 13 of 27


Requirements Document

2.11 Cart
In the cart screen, the user will have the following details available.

o Quantity
o Food Fee
o Delivery Fee
o Add voucher
o Total Price
o Contact info
o Delivery address
o Payment
 Cash on Delivery
 Credit or debit card

2.12 Online Payment

In case the user wants to pay online user will have to enter the following
information.

o Name on Card
o Card Number
o Card expiry month and year
o CVC

2.13 Feedback

Upon the completion of each order, a notification will be sent to the user/
end-customers to give feedback about food and application.

2.14 Ratings

The user would have provided to give a rating to order on the star rating
basis. The following will be the aspects of the order.

o Delivery time
o Rider attitude
o Food Quality
o Packaging
Last Modified: 11/25/2019 Page 14 of 27
Requirements Document

Last Modified: 11/25/2019 Page 15 of 27


Requirements Document

3 Restaurants Registration
3.1 Overview

Restaurants can be registered on this food delivery system conveniently by


filling out the details of their restaurants and selecting packages by offers by
food Delivery Company, once the restaurant profile approved by the admin.
Restaurants owners can start uploading their meals, categories, attributes,
cuisines type, prices and delivery fee and time.

3.2 Modules
The restaurant's management system will have the following module.

o Register Restaurant
o Sign in
o Restaurant Profile
o Food items
o Categories
o Orders
o Accounts
o Report

Last Modified: 11/25/2019 Page 16 of 27


Requirements Document

3.3 Restaurants Registration Form.

The following will be the details required to register their restaurants.

o Restaurants Name
o Restaurant Email
o Phone Number
o City
o State
o Zip Code
o Business Days
o Timings
o Images
o Password

3.4 Work Flow

Last Modified: 11/25/2019 Page 17 of 27


Requirements Document

3.5 Add Meal

The restaurant manager will have the rights to create, update & delete. The
following will be the data fields required to add a meal.
o Food name
o Food Images
o Select Food Category
 If the category isn't previously created then create a new
category.
o Food description
o Food Price
o Food status
o Food Discounted prices

3.6 Category

Manger user will have the provision to see food categories detail in this
section & the user will have the right to create a new category as well as he
can edit & delete any categories and sub-categories.
The categories table will have the following details.
o S. no
o Category
o Sub Category
o Action
 Edit
 Delete

3.7 Orders

Manger users will have the provision see the orders coming from the front
end customer and entertain the customer based on their orders. In the case of
cash on delivery manager user will have the provision to either accept or
reject the order. In case of online payment, orders can be auto accepted and
that would mean that all accepted orders absolutely have to be catered to the
customer. Manager users will be able to update the order status & the
customer can see there order status on their mobile application.

Last Modified: 11/25/2019 Page 18 of 27


Requirements Document

Orders page will have a search bar to search for the order based on the order
id.

Last Modified: 11/25/2019 Page 19 of 27


Requirements Document

Order status

Users can easily filter out orders based on their status. The following will be
the order status.

o Assigned
o Pending
o Accepted
o Delivered
o Total Orders

Orders Details.

The user will be to the following details coming from front end customer
application.

o Orders id
o Name
o Email
o Phone
o Location
o Food name
o Qty
o Date & time
o Order price
o Order status

3.8 Reports

The restaurant's Manager will have the provision to see the payment reports
of their restaurants. In this page users will be able to see sales reports, users
can either download the report in xlx format or view them. This report will
consist of the following details.

o S no.
o Order id
o Date
o Amount

Last Modified: 11/25/2019 Page 20 of 27


Requirements Document

o Status

3.9 Rider Interface

The food delivery person will able to log in based on his credentials and see
his assign orders, Every time order is assigned to riders will get a
notification. Rider will have a live map view to track customer location as
the rider delivers the orders, the rider will have the provision to end the order
and rate the customer.

4 Super Admin Interface


4.1 Overview

Admin would have a provision of the dashboard where he can have an


overview of the app functioning with orders, restaurants, payments and
related ratings to orders and revenue of the month. This super admin
interface will have the provision activate or deactivate restaurants as well as
this super admin can see all the details regards to orders, sales, payments,
and front end, the customer.

4.2 Modules

The following will be the module s in the super admin interface.

o Users
o Resturants
o Restaurants request
o Payment
o Notification
o Coupons
o About us
o Terms of services

Last Modified: 11/25/2019 Page 21 of 27


Requirements Document

o Logout

Last Modified: 11/25/2019 Page 22 of 27


Requirements Document

Users

Admin will have the provisions to see the front end customers' details & he
can also activate or deactivate the customers. The following information will
be available on this page.

o Name
o Email
o Number
o Orders
o Action
 Activate user
 Deactivte user

4.3 Restaurants.

In this section, the admin will be able to see all the restaurants registered
with them as well as their orders & their sales. This super admin will have
the provision to change their status either to active or de-active any
restaurants as well as the admin will be able to update the payment sharing
percentage for the restaurants.

o Name
o Email
o Number
o Orders
o Payments
 Total Price
 Resturant Share
 Admin Share
o Action
 Activate user
 Deactivate user
o View

Last Modified: 11/25/2019 Page 23 of 27


Requirements Document

4.4 restaurants request


When the user registers their restaurants to our system account approval
notification will come on this super admin interface and this super admin
will have the provision to either approved or disapproved.

4.5 Coupons

Admin will have the provision to create coupons. Coupons are a great way
to offer discounts and rewards to your customers and can help promote sales
across your shop. To Create coupons admin will have to follow these steps.

o Create Coupons
o Coupon Code
o Coupon Type
o Coupon amount
 This coupon amount will automatically add the discount to the
customer bill amount.
o Select segment user
 Users
 Restaurnst
o Expiry date

4.6 Payments

Super admin will be able to see all the payments detail of all the restaurants
and all the orders they have catered. Admin would be allowed to track and
monitor the activities of customers and restaurants. There would be a certain
% amount to be shared with admin on each payment transaction from
restaurants end. A certain amount of admin share per orders would be
defined by admin as per the orders catered. Following will be the details
admin would be able to see in the dashboard.

o Restaurants name
o Email
o Phone Contact
o Admin %
o Action

Last Modified: 11/25/2019 Page 24 of 27


Requirements Document

 view

Last Modified: 11/25/2019 Page 25 of 27


Requirements Document

4.7 Notification

Admin will be able to add push notification for users and restaurants. Push
notifications enable you to communicate brief yet important alerts to your
users.
The Push module on the system makes it easy to set up push campaigns to
all your users or specific user segments
The next step would be to indicate the target audience for your push
campaign i.e: restaurants or users.

o Image
o Title
o Target Audience
o Description

4.8 Terms & services

It would be defined from the admin panel for the usage of the app. Help
regarding app utilization will also be mentioned here.

4.9 About us
Admin will have the provision to give a description of the company in this
section & the customer will be able this description in their app.

4.10 Logout
Admin can log out of the system

Last Modified: 11/25/2019 Page 26 of 27


Requirements Document

Last Modified: 11/25/2019 Page 27 of 27

Das könnte Ihnen auch gefallen