Project statement for Online food delivery

Introduction

Software that enables the restaurant to accept and handle online orders is known as an online ordering infrastructure. A typical online meal ordering system consists of two parts: a website or app where consumers can examine the menu and make orders, and the interface of the admin where the restaurant can take orders and process them.

“Online food delivery systems” are needed to control the management of the food delivery store. The owner of the business by observing the system can track the sales, can manage the sold item, and also can track the most sales for a specific product.

Online food delivery system provides a huge range of benefits that saves time as well as money for customers. Using online orders for food delivery makes the order process easier.

The system of online ordering is more efficient for managing customers and food orders than manual food ordering. While ordering food by the use of online mode the data of the customer must be saved by the database of the company’s system which will recommend future food order services with delicious food items.

Any restaurant with the order service better reaches new customers with their great service, so the order food delivery system also provides cheap marketing.

The owner of the business can keep track of the online food delivery system from inside the store without going anywhere. Besides business owners can also keep track of the locality of the customers or from where the order has been placed or to where the order will go; whom companies are able to reach.

The main benefit of using an online food delivery system is anyone can explore new food from the different locations of the nearby area. In addition to the growing demand of the customer in this era, the restaurant can stay ahead in the middle of the competition who are investing in such type of online food system mechanism.

In this report of the project, the admin is present who mainly controls all the tasks which have linked with the management process. The admin in this study plays a vital role who is controlling the majority of the task inside the online delivery system such as keeping track of sales, can managing the food order.

The business owner can manage the payment process of the customer and can view the feedback from the feedback page where the customer gave feedback based on the service they provided.

Aims and Objectives

Aims: 

The aim of this study is to grow an online food delivery system that can help to manage the online food delivery process in a restaurant.

Objectives:

The objectives of the given study are:

• To create a system for online food delivery from the restaurant
• To track the sales
• To track the payment process of the system
• To manage the different items for the food item
• To develop an infrastructure for online food delivery
• To generate a report based on the online food delivery system

Functionalities of the “Online food delivery system”

The functionalities of the online food delivery system are written below which must be carried out by the system of “online food management system”:

• Management of food depending on the order of the customer
• Keeping track of the Sales
• Helpful for the end-users for ordering the food
• Using an online food delivery system to reach new customers easily
• Online food delivery system easily increases the business growth
• Using an online food delivery system time and money are also saved
• Managing the payment process of the customer (Cicco et al. 2021)
• Add, edit, view, and listing of the food items
• Feedback helps to overcome the faults
• Online payment makes an easy transaction for the customer
• Viewing the customer feedback from the feedback page
• Report generation which is related to the different food items has been ordered from the various location of the customer (Das, 2018).

Project description for Online food delivery

An online food delivery system is beneficial for users to order food according to their preference, so developers think to develop an app to mitigate the problem of the users.

This online food delivery system provides an outstanding benefit to users in all aspects.

The above-mentioned food delivery app is created followed by some unique steps all steps are described in detail so that the users understand the process in depth for upgrading their knowledge and can utilize their time by ordering mouth-watering food items in online mode.

Below all steps are described elaborately:

Dashboard for managing food:

In these steps, the developer creates a dashboard page to manage all food items easily. In those steps, basically who can control this whole system, who can directly connected to the system who instructs the system to work according to the requirement can be defines.

At first, the admin request the system to create the managed food options then the system meets the requirements according to the admin’s requests.

In the second step, the admin adds all types of choices like Chinese items, Thai dishes, Indian dishes and followed by more items then the system shows all the choices on the create dashboard page.

After showing all the choices admin press the required button for further process. All data is saved into the database of the system so that anyone can fetch the data at any point in time (Aprilianti and Amanta, 2020).

After processing all steps system generate a confirmation SMS that is received by the admin and lastly the managing food category is created for the desired app “online food delivery”.

After creating the managing food option, the admin requested the system to add one more option for “Adding new food items” to add all food items according to the best-selling preferences. The system provides the required option for adding food items according to the admin’s requirements.

Then admin adds a food items option to the “managing food” category. All required data is further saved into the system’s database for future upgradation. After doing all steps, the system generates a confirmation SMS for further proceeding. Then finally, one more option the “add food items” option is generated (Ali et al. 2020).

Similarly, for editing the food items details admin requested the systems to generate an option to create one more button for “editing food items details”. According to the admin’s request, the system generates a button to edit all food items.

After that, the admin adds another option “edits food items details” and all required data is saved into the database for further necessity. Then as usual system generate another confirmation SMS for further upgradation.

Another option “editing food items details” button is created to edit all food items’ details if needed. After creating the “editing food items details” options admin wants to add one more option which is “view food item details” for viewing all food items details on the dashboard.

Admin is requested to the system to add a “view food items details” option for showing all the details, then the system has added another option for showing the food items details after adding the option admin can easily add view button into the “editing food items” options, thereafter, one confirmation SMS is received by both admin and systems (Sidharta, 2021). In the last step, “view foot items details” is also added to these apps.

Now, for listing all the food item details admin wants to add another button that is “Listing food item details” to list all food items details for choosing the food items easily.

So to create the listing food item details option admin requests the system to create the last option “listing food items details” and then the admin easily adds that option after adding the view food item details option.

Admin and system both received the confirmation SMS. At last, “listing food items details” is created for the desired app. Finally, the developer develop the manage food option on the dashboard page.

 

Use case for Log-in:

Figure 1: Use-case for log-in

 

Use case Description for Feedback:

Case name	Log-in for admin
Condition	Admin needs to fill in the details to Log-in
Event	The log-in form required valid credentials from the admin to access the home page
Description	Admin requests to log in to the home page to access the online food delivery system
Actors	Admin
Preconditions	Admin must click on the submit button.
Postconditions	Admin must click on the submit button.
The flow of the activities	Admin	System
	1. Admin request for a log-in page.	1. Provides the log-in page.
	2. Press the submit button as per the requirement.	2. The details must be checked from the database.
	3. Successfully logged in to the home page.	3. Successfully logged in to the home page.
Exception condition	The page cannot be accessed or the button cannot be clicked without valid credentials

Table 1: Activity Description for the log-in page

 

Screen for Log-in page:

Figure 2: Screen for the log-in page

 

Sequence diagram for the Feedback:

Figure 3: Sequence diagram for Log-in

 

Activity diagram for Log-in page:

Figure 4: Activity diagram for Log-in page

 

Usecase for Password change page:

Figure 5: Use case for the Password change page

 

Use case Description for Password change page:

Case Name	Reset password for admin
Condition	Admin needs to fill in a new password and confirm it
Event	The Reset password form requires a new password from the admin and confirm it
Description	The password can be changed based on a new password and new details should be stored in the database
Actors	Admin
Preconditions	Admin should click on the Reset button
Postconditions	Admin should click on the Reset button
The flow of the activities	Admin	System
	1. Admin requests to change the password.	1. Provides the reset password page and requires a new password to confirm
	2. Press the reset button as per the requirement.	2. New details must be stored in the database for login purposes
	3. Successfully logged in to the home page.	3. Successfully changed the password and updated the database.
Exception condition	The home page can not be accessed if both the existing and new passwords are the same.

Table 2: Activity Description for Password change page

 

Screen for Password change page:

Figure 6: Screen for Password change page

 

Sequence diagram for Password change page:

Figure 7: Sequence diagram for Password change page

 

Activity diagram for Password change page:

Figure 8: Activity diagram for Password change page

 

Use case diagram for logout page:

Figure 9: Use case diagram for logout page

 

Use case Description for Password change page:

Case name	Logout for admin
Condition	Admin needs to confirm before logout the food delivery system
Event	The logout page requires permission from the admin and confirm logging out
Description	The logout page has a checkbox for confirmation and cancelation of logging out
Actors	Admin
Preconditions	Admin should click on the confirm or cancel button
Postconditions	Admin should click on the confirm or cancel button
The flow of the activities	Admin	System
	1. Admin requests to log out.	1. System asks for a confirmation.
	2. Press the confirm to cancel button.	2. Processes the input for the admin.
	3. Successfully logged out or canceled.	3. Registered as logged out.
Exception condition	There must be a confirmation for logging out of the page from the admin site.

Table 3: Activity Description for Logout page

 

Screen diagram for logout page:

Figure 10: Screen diagram for logout page

 

Sequence diagram for logout page:

Figure 11: Sequence diagram for logout page

 

Activity diagram for logout page:

Figure 12: Activity diagram for logout page

 

Use case diagram for Dashboard for admin:

Figure 13: Use case diagram for admin dashboard

 

Use case Description for Admin Dashboard:

Case name	Dashboard for admin
Condition	Admin needs to log in and access the functionalities of the dashboard page
Event	The dashboard page offers several managing criteria from the admin front.
Description	Admin can manage food details, order details, payment details, and feedback as per their requirements.
Actors	Admin
Preconditions	Admin should log in first to access the dashboard and then manage the details of food delivery.
Postconditions	Admin can access the details related to delivery.
The flow of the activities	Admin	System
	1. Admin requests to log in	1. System asks for credentials.
	2. Logged in successfully.	2. Give access to the dashboard page.
	3. Manage the food delivery-related details.	3. Manage the database as per the requirements of the admin.
Exception condition	There must be a successful log-in to access the dashboard page for the admin otherwise admins can not access the details.

Table 4: Activity Description for Admin Dashboard

 

Screen diagram for Admin Dashboard:

Figure 14: Screen for Admin Dashboard

 

Sequence diagram for Admin Dashboard:

Figure 15: Sequence diagram for Admin Dashboard

 

 

Activity diagram for admin Dashboard:

Figure 16: Activity diagram for Admin Dashboard

 

Use-case for the Manage foods:

Figure 17: Use-case for the manage foods

Use case Description for Manage foods:

Case name	Enter inside the manage foods
Condition	Admin wants to enter inside the manage foods
Event	The option can be chosen by admin from the available options.
Description	As per the requirement user should provide click on the manage foods.
Actors	Admin
Preconditions	Admin must choose and click on the button.
Postconditions	Admin must choose and click on the button.
The flow of the activities	Admin	System
	1. Admin request for a manage foods page.	1. Enter choices in managing foods like veg,non-veg, etc.
	2. Press the button as per the requirement.	2. The details must be saved in the database.
	3. Conformation will come from the database.	3. Successful entry into other pages through the manage foods buttons
Exception condition	If the order id correct button does not get pressed as per the requirement.

Table 5: Activity Description for the Manage foods page

 

Screen report page for manage foods:

Figure 18: Screen for the Manage foods page

Sequence diagram for the manage foods:

Figure 19: Sequence diagram for “Manage foods”

Activity diagram for the manage foods page:

Figure 20: Activity diagram for the manage foods page

Use case for managing order:

Figure 21: Use-case for the manage ordersUse case Description for Manage orders:

Case name	Enter inside the manage orders
Condition	Admin wants to enter inside the manage orders
Event	The option can be chosen by admin from the available options.
Description	As per the requirement user should provide click on the manage orders.
Actors	Admin
Preconditions	Admin must choose and click on the button.
Postconditions	Admin must choose and click on the button.
The flow of the activities	Admin	System
	1. Admin request for a manage orders page.	1. Enter choices in managing food orders like veg,non-veg, etc.
	2. Press the button as per the requirement.	2. The details must be saved in the database.
	3. Conformation will come from the database.	3. Successful entry into other pages through the manage orders buttons
Exception condition	If the order id correct button does not get pressed as per the requirement.

Table 6: Activity Description for the Manage orders page

 Screen report page for manage orders:

Figure 22: Screen for the Manage order page

Sequence diagram for the manage orders:

Figure 23: Sequence diagram for “Manage order”

Activity diagram for the manage orders page:

Figure 24: Activity diagram for the manage or

Use case Description for Manage payments:

 

Case name	Enter inside the manage payments.
Condition	Admin wants to enter inside the manage payments.
Event	The option can be chosen by the admin from the available payment options.
Description	As per the requirement user should provide click on the manage payments.
Actors	Admin
Preconditions	Admin must choose and click on the button.
Postconditions	Admin must choose and click on the button.
The flow of the activities	Admin	System
	1. Admin request for a manage payment page.	1. Enter choices in managing payment in food orders.
	2. Press the button as per the requirement.	2. The details must be saved in the database.
	3. Conformation will come from the database.	3. Successful entry into other pages through the manage payment buttons
Exception condition	If the order id correct button does not get pressed as per the requirement.

Table 7: Activity Description for the Manage payment page

 

Screen report page for manage payments:

Figure 26: Screen for the Manage payments page

Sequence diagram for the manage payments:

Figure 27: Sequence diagram for “Manage payments ”

 

Activity diagram for the manage payment page:

Figure 28: Activity diagram for the manage payment page

Use case for Feedback:

Figure 29: Use-case for the feedback

Use case Description for Feedback:

Case name	Enter feedback.
Condition	Admin wants to enter Feedback.
Event	The option can be chosen by the admin from the available Feedback options.
Description	As per the requirement user should provide click on Feedback.
Actors	Admin
Preconditions	Admin must choose and click on the button.
Postconditions	Admin must choose and click on the button.
The flow of the activities	Admin	System
	1. Admin request for a feedback page.	1. Enter choices feedback in food orders.
	2. Press the button as per the requirement.	2. The details must be saved in the database.
	3. Conformation will come from the database.	3. Successful entry into other pages through the feedback buttons
Exception condition	If the order id correct button does not get pressed as per the requirement.

Table 8: Activity Description for the Feedback page

 

Screen report page for Feedback:

Figure 30: Screen for the feedback page

Sequence diagram for the Feedback:

Figure 31: Sequence diagram for “Feedback ”

 

Activity diagram for the Feedback page:

Figure 32: Activity diagram for the Feedback page

Use case diagram for add new order

Figure 33: Use case diagram for add new order

 

Use Case Description for add new order

Case name	Add new order.
Condition	Admin wants to add a new order.
Event	Admin can get insight into adding a new order.
Description	The user must provide a valid user id and password, after that they add a new order.
Actors	Admin
Preconditions	The admin must provide a valid user id and password to receive the successful page.
Postconditions	The admin provides a successful page to add a new order.
The flow of the activities	Admin	System
	1. Admin request for adding new orders.	1. Instruct the system to show the insight
	2. The number of order fields must be filled.	2. The details must be saved in the database.
	3. Conformation will be received from the database.	3. Successful viewing of the adding new orders page and category data is shown on the admin side.
Exception condition	The user id or password is not matched.

Table 9: Use Case Description

Screen diagram for adding new order

Figure 34: Screen diagram for adding new order

Activity diagram for adding new order

 

Figure 35: Activity diagram for adding new order

 

Sequence diagram for adding new orders

Figure 36: Sequence diagram for adding new orders

 Use case diagram for edit delivery details of order

 

Figure 37: Use case diagram for edit delivery details of order

 

Use Case Description for edit delivery details of order

Case name	Edit delivery details of an order.
Condition	Admin wants to edit the delivery details of an order.
Event	Admin can get insight into editing the delivery details of an order.
Description	The user must provide a valid user id and password, after which they edit the delivery details of an order.
Actors	Admin
Preconditions	The admin must provide a valid user id and password to receive the successful page.
Postconditions	The admin provides a successful page to edit the delivery details of an order.
The flow of the activities	Admin	System
	1. Admin requests to edit the delivery details of an order.	1. Instruct the system to show the insight
	2. The number of edit fields must be filled.	2. The details must be saved in the database.
	3. Conformation will be received from the database.	3. Successful viewing of the edit of the delivery details of an order page and category data is shown on the admin side.
Exception condition	The user id or password is not matched.

Table 10: Use Case Description

 

Screen diagram for edit delivery details of order

Figure 38: Screen diagram for edit delivery details of order

 

Activity diagram for edit delivery details of order

Figure 39: Activity diagram for edit delivery details of order

 

Sequence diagram for edit delivery details of order

 

Figure 40: Sequence diagram for edit delivery details of order

 

 

Use case diagram for view order details

Figure 41: Use case diagram for view order details

 

 

Use Case Description for view order details

Case name	View order details.
Condition	Admin wants to view order details.
Event	Admin can get insight into view order details.
Description	The user must provide a valid user id and password, after that view order details.
Actors	Admin
Preconditions	The admin must provide a valid user id and password to receive the successful page.
Postconditions	The admin provides a successful page to view order details.
The flow of the activities	Admin	System
	1. Admin requests to view order details.	1. Instruct the system to show the insight
	2. The number of view fields must be filled.	2. The details must be saved in the database.
	3. Conformation will be received from the database.	3. Successful viewing of the “view order details” page and category data is shown on the admin side.
Exception condition	The user id or password is not matched.

Table 11: Use Case Description

Screen diagram for View Order Details

Figure 42: Screen diagram for View Order Details

 

 

Activity diagram for View Order Details

Figure 43: Activity diagram for View Order Details

 

Sequence Diagram for View Order Details

Figure 44: Sequence Diagram for View Order Details

 

 

Use case diagram for listing all orders

Figure 45: Use case diagram for listing all orders

Use Case Description for Listing all orders

Case name	Listing all orders.
Condition	Admin wants to list all orders.
Event	Admin can get insight into listing all orders.
Description	The user must provide a valid user id and password, after that list all orders.
Actors	Admin
Preconditions	The admin must provide a valid user id and password to receive the successful page.
Postconditions	The admin provides a successful page for listing all orders.
The flow of the activities	Admin	System
	1. Admin requests to list all orders.	1. Instruct the system to show the insight
	2. The number of list fields must be filled.	2. The details must be saved in the database.
	3. Conformation will be received from the database.	3. Successful viewing of the “listing all orders” page and category data is shown on the admin side.
Exception condition	The user id or password is not matched.

Table 12: Use Case Description

Screen diagram for Listing all orders

Figure 46: Screen diagram for Listing all orders

 

Activity diagram for Listing all orders

 

Figure 47: Activity diagram for Listing all orders

Sequence Diagram for listing all orders

Figure 48: Sequence Diagram for listing all orders

 

 

Use-case for adding food items:

 

Figure 49: Use-case for adding food items

Use-case description for adding food items:

Case Name:	Enter inside the food items
Condition:	Admin wants to add food items
Event:	Option can be chosen by the admin for adding food items
Description:	As per the client’s requirement user should click on the provided button “add food items”
Actors:	Admin
Preconditions:	Admin must able to click on the created button
Postconditions:	Admin must able to click on the created button
The flow of the activities:	Admin	System
	Admin request for adding food item options	System shows the required option for adding food items
	Admin add new food items	All details saved into the database
	Confirmation will come from the system	Successfully created options for adding new food items.
Exception condition:	Button need not get pressed if the name of the food is correctly entered.

Table 13: Use-case description for adding food items 

 

 

Screen report for adding food items:

Figure 50: Screen report for adding food items

Sequence diagram for adding food details:

Figure 51: Sequence diagram for adding food items

Activity diagram for adding food items:

Figure 52: Activity diagram for adding food items

Use-case for editing food items details:

Figure 53: Use-case for editing food items details

Use-case description for editing food items details:

Case Name:	Enter the edited food items details
Condition:	Admin wants to edit food items details
Event:	Option can be chosen by the admin for editing food items details
Description:	As per the client’s requirement user should click on the provided button “edit food items”
Actors:	Admin
Preconditions:	Admin must able to click on the created button
Postconditions:	Admin must able to click on the created button
The flow of the activities:	Admin	System
	Admin request for editing food item options	System shows the required option for editing food items
	Admin edit new food items	All details saved into the database
	Confirmation will come from the system	Successfully created options for editing new food items details.
Exception condition:	Button need not get pressed if the name of the food is correctly entered.

Table 14: Use-case description for editing food items detail

Screen report for editing food items details:

Figure 54: Screen report for editing food items details 

Sequence diagram for editing food items details:

Figure 55: Sequence diagram for adding food items details

Activity diagram for editing food items details:

Figure 56: Activity diagram for editing food items details

Use-case diagram for view food details of manage food:

Figure 57: Use-case diagram for view food details of manage food

Description to view food details and manage foods

Case Name	Enter inside the view food details
Condition	Admin wants to enter inside the view food details of manage foods.
Event	The options can be chosen by the admin to view food details of managed food.
Description	As per the client’s requirement user should click on the provided button “view food details”.
Actors	Admin
Preconditions	Admin must be able to click on the created button.
Postconditions	Admin must be able to click on the created button.
The flow of the activities	Admin	System
	1. Admin request for view food details of manage foods	1. Prompts the admin to enter the choice of getting view food details data
	2. Press the button as per requirement	2. Take the information from the admin and store it inside the database
	3. Get confirmation from the system	3. Submit a report of view food details successful
Exception	Button need not get pressed if the name of the food is correctly

Table 15: Activity Description for the view food details of manage foods 

Screen diagram for viewing food details of manage foods

Figure 58: Screen diagram for viewing food details of manage foods

 

 

Sequence diagram for viewing food details of the manage foods

Figure 59: Screen report page for viewing food details of manage foods

 

 

Activity diagram for viewing food details of the manage foods page

Figure 60: Activity diagram for  viewing food details of the manage foods page

 

 

Use-case diagram for listing food items of managed food:

Figure 61: Use-case diagram for listing food items of managed food

 

 

Description to listing food items and manages foods

Case Name	Enter inside the listing food items
Condition	Admin wants to enter inside the listing food items of managed food.
Event	The options can be chosen by the admin to list food items of managed food.
Description	As per the client’s requirement user should click on the provided button “listing food items”.
Actors	Admin
Preconditions	Admin must be able to click on the created button.
Postconditions	Admin must be able to click on the created button.
The flow of the activities	Admin	System
	1. Admin request for listing food items of managed foods	1. Prompts the admin to enter the choice of getting listing food items data
	2. Press the button as per requirement	2. Take the information from the admin and store it inside the database
	3. Get confirmation from the system	3. Submit a report of listing food items successful
Exception	Button need not get pressed if the name of the food is correctly

Table 16: Description for the Listing food items of manage foods

 

 

Screen diagram for listing food items of managed food

Figure 62: Screen diagram for listing food items of managed food

 

 

Sequence diagram for listing food items of the managed food

Figure 63: Sequence diagram for listing food items of the managed food

 

 

Activity diagram for listing food items on the manage foods page

Figure 64: Activity diagram for listing food items on the manage foods page

 

 

 

Use-case diagram for adding new payment

Figure 65: Use-case diagram for adding new payment

 

Use case for a description of adding new payment

Case name	Adding new payment
Condition	Admin wants to add new payment
Event	Admin completed the login field for adding a new payment
Description	The user must provide a valid user id and password, after that the adding new payment page will appear.
Actors	Admin
Preconditions	Admin must provide a valid user id and password.
Postconditions	Admin receives the successful page for adding a new payment.
The flow of the activities	Admin	System
	1. Admin request for adding new payment	1. Instruct the system to prompt the admin to add a new payment
	2. The number of payments must be filled.	2. The details must be saved in the database.
	3. Conformation will be generated from the database.	3. Successful addition of a new payment page is shown on the admin side.
Exception condition	The new payment may not be added successfully.

Table 17: Description of adding new payment

 

Screen for adding new payment

Figure 66: Screen for adding new payment

 

Sequence diagram for adding new payment

Figure 67: Sequence diagram for adding new payment

 

Activity diagram for adding new payment details

Figure 68: Activity diagram for adding new payment details

 

Use-case diagram for editing the existing payment record

Figure 69: Use-case diagram for editing the existing payment record

 

Description for editing the existing payment record

Case name	Editing of the Existing payment record
Condition	Admin wants to edit the existing payment record
Event	Admin has successfully completed the login field for the editing of the existing payment record
Description	The user should give a valid user id and password, after that the edit of the existing payment records and edited payment page will appear.
Actors	Admin
Preconditions	Admin should give a valid user id and password.
Postconditions	Admin receives the successful page for the editing of the existing payment record.
The flow of the activities	Admin	System
	1. Admin requests for the editing of the existing payment record	1. Instruct the system to edit the existing payment record
	2. The edits and existing payment records should be filled in correctly.	2. The details have to be saved in the database.
	3. Conformation will be generated from the database.	3. Successful editing of the existing  payment record page is shown on the admin side.
Exception condition	The editing of the existing payment record may not be added successfully.

                              Table 18: Description of Edit the Existing Payment Record

Screen for editing the existing payment record

                Figure 70: Screen for editing the existing payment record

 

Sequence diagram for editing the existing payment record

Figure 71: Sequence diagram for editing the existing payment record

 

Activity diagram for editing the existing payment record

Figure 72: Activity diagram for editing the existing payment record

 

Use-case diagram for view details of payment

Figure 73: Use-case diagram for view details of payment

 

Description for view details of payment

Case name	View details of the payment
Condition	Admin wishes to view details of the payment
Event	Admin completed the login field for the view details of the payment
Description	The user should provide a valid user id and password, after that the view details of the payment page will appear.
Actors	Admin
Preconditions	Admin should give a valid user id and password.
Postconditions	Admin gets the successful page for the view details of the payment
The flow of the activities	Admin	System
	1. Admin request for a view of payment	1. Instruct the system to view details of the details payment
	2. A details view of the payment should be selected.	2. The details should be saved in the database.
	3. Confirmation will be received from the database.	3. Successful viewing details of the payment page are shown on the admin side.
Exception condition	The view details of the payment may not be added successfully.

Table 19: Description for view details of payment

 

Screen for a view of details of the payment

Figure 74: Screen for a view of details of the payment

 

Sequence diagram for a view of details of the payment

Figure 75: Sequence diagram for a view of details of the payment

 

Activity diagram for details views details of the payment

Figure 76: Activity diagram for details views details of the payment

 

Use-case diagram for the listing of all payment

Figure 77: Use-case diagram for the listing of all payment

 

Description for list of all payment

Case name	Listing of all payment
Condition	Admin wants to list all payments
Event	Admin completed the login field for a listing of all payments
Description	The user must provide a valid user id and password, after that the adding listing of the payments
Actors	Admin
Preconditions	Admin should give a valid user id and password.
Postconditions	Admin gets the successful page for adding the list of payments
The flow of the activities	Admin	System
	1. Admin request for the list of all payments.	1. Instruct the system to add the list of payments.
	2. The list of all payments must be selected.	2. The details must be saved in the database.
	3. Conformation will be received from the database.	3. Successful listing of all payment pages is shown on the admin side.
Exception condition	Completed the login field for adding a listing of all payments.

Table 20: Description of the list of all payments

 

Screen for viewing the details of the list of the payments

Figure 78: Screen for viewing the details of the list of all the payments

 

Sequence diagram for the list of all payments

Figure 79: Sequence diagram for the list of all payments

 

Activity diagram for the list of all payments

Figure 80: Activity diagram for the list of all payments

 

 

Use case diagram for feedback on food quality

Figure 81: Use case diagram for viewing feedback on food quality

 

 

Use case Description for Feedback on food quality

Case name	Viewing feedback for food quality
Condition	Admin wants to view feedback for food quality
Event	Admin completed the login field for viewing feedback for food quality.
Description	The user must provide a proper user id and password, after that viewing feedback for the food quality page will appear.
Actors	Admin
Preconditions	Admin must offer an appropriate id of the user and password.
Postconditions	Admin receives the successful page for viewing feedback for food quality.
The flow of the activities	Admin	System
	1. Admin requests for viewing feedback for food quality.	1. Instruct the system to provide a view for feedback on food quality.
	2. The details must be filled in.	2. The details must be saved in the database of the system.
	3. Conformation will be received from the system of the database.	3. Successful viewing feedback for food quality is shown on the admin side.
Exception condition	If the order id is not matched with the database of the system.

Table 21: Description for viewing feedback on food quality

 

 

Screen diagram for a feedback page on food quality

Figure 82: Screen for viewing feedback on food quality

 

 

Sequence diagram for the Feedback on food quality

Figure 83: Sequence diagram for viewing feedback on food quality

 

 

Activity diagram for the Feedback page on food quality

Figure 84: Activity diagram for viewing feedback on food quality

 

 

Use case for feedback for the delivery process

Figure 85: Use case diagram for viewing feedback on the delivery process

 

 

Use case Description for Feedback on delivery process

Case name	Viewing feedback for delivery process
Condition	Admin wants to view feedback for the delivery process.
Event	Admin completed the login field for viewing feedback for the delivery process.
Description	The user must provide a proper user id and password, after that the viewing feedback for the delivery process page will appear.
Actors	Admin
Preconditions	Admin must give an appropriate user id and password.
Postconditions	Admin receives the successful page for viewing feedback for the delivery process.
The flow of the activities	Admin	System
	1. Admin requests for viewing feedback for the delivery process.	1. Instruct the system to view feedback for the delivery process.
	2. The details must be filled in.	2. The details must be saved in the database of the system.
	3. Conformation will be received from the database of the system.	3. Successful viewing feedback for the delivery process page is shown on the admin side.
Exception condition	If the order id is not matched with the database.

Table 22: Description for viewing feedback on the delivery process

 

 

Screen diagram for a feedback page on the delivery process

Figure 86: Screen for viewing feedback on the delivery process

 

 

Sequence diagram for the Feedback on the delivery process

Figure 87: Sequence diagram for viewing feedback on the delivery process

 

 

Activity diagram for the Feedback page on the delivery process

Figure 88: Activity diagram for viewing feedback on delivery process

 

 

Use case for feedback for the payment process

Figure 89: Use case diagram for viewing feedback on payment process

 

 

Use case Description for Feedback on payment process

Case name	Viewing feedback for payment process
Condition	Admin wants to view feedback for the payment process.
Event	Admin completed the login field for viewing feedback for the payment process.
Description	The user must provide a proper user id and password, after that the viewing feedback for the payment process page will appear.
Actors	Admin
Preconditions	Admin must give an appropriate user id and password.
Postconditions	Admin receives the successful page for viewing feedback for the payment process.
The flow of the activities	Admin	System
	1. Admin requests for viewing feedback for the payment process.	1. Instruct the system to view feedback for the payment process.
	2. The details must be filled in.	2. The details must be saved in the database of the system.
	3. Conformation will be received from the database of the system.	3. Successful viewing feedback for the payment process page is shown on the admin side.
Exception condition	If the order id is not matched with the database.

Table 23: Description for viewing feedback on payment process

 

 

Screen diagram for a feedback page on the payment process

Figure 90: Screen for viewing feedback on payment process

 

 

Sequence diagram for the Feedback on the payment process

Figure 91: Sequence diagram for viewing feedback on payment process

 

 

Activity diagram for the Feedback page on the payment process

Figure 92: Activity diagram for viewing feedback on the payment process

 

 

ER Diagram for online food delivery system

Figure 93: ER Diagram

 

 

Reference

Ali, S., Khalid, N., Javed, H.M.U. and Islam, D.M.Z., 2020. Consumer adoption of online food delivery ordering (OFDO) services in Pakistan: The impact of the COVID-19 pandemic situation. Journal of Open Innovation: Technology, Market, and Complexity, 7(1), p.10.

Aprilianti, I. and Amanta, F., 2020. Promoting Food Safety in Indonesia’s Online Food Delivery Services (No. 28). Policy Paper.

Das, J., 2018. Consumer perception towards “online food ordering and delivery services”: an empirical study. Journal of Management (JOM), 5(5), pp.155-163.

De Cicco, R., Silva, S.C.L.D.C.E. and Alparone, F.R., 2021. “It’s on its way”: Chatbots applied for online food delivery services, social or task-oriented interaction style?. Journal of Foodservice Business Research, 24(2), pp.140-164.

Sidharta, S.M., 2021. Customer Loyalty Analysis on Online Food Delivery Services. Turkish Journal of Computer and Mathematics Education (TURCOMAT), 12(3), pp.4003-4013.