微信客服：xiaoxionga100
微信客服：ITCS521
INFS7007-无代写
时间：2023-10-30
INFS7007 - Intelligent Business Analysis
Final Report
Business Analysis of the Food Delivery System
-Ele.me
Business Analysis of the Ele.me System
Page 2 of 38
Executive summary
Nowadays, food delivery service is more and more popular. Consumers are willing to pay additional delivery fees
to enjoy the service of delivering food to their door. In addition, the coronavirus pandemic has catalysed this trend,
and this service have facilitated people's lives. In China, the food delivery service is very mature, and the Ele.me
platform is one of the most popular food delivery systems. Through the requirements analysis, we understand the
expectations of relevant stakeholders for the food delivery system. To respond to these expectations, the Ele.me
food delivery system mainly implements four major functions. First, in order to effectively control food safety issues,
this system must be able to verify the qualifications of merchants and deliverers. If the merchant does not have a
legal operating permit or the delivery staff is unhealthy, it will affect the quality of delivery service. Second, this
system allows users who play different roles to create account for different purpose. For example, the deliverer
account mainly used for allowing deliverers to receive match request and track the delivery process, while the
customer account mainly used for allowing customers to place orders. Third, this system must implement online
order placement and order processing functions. This function allows consumers and merchants to achieve
barrier-free remote communication by transmitting detailed information about the order. Fourth, this system
guarantees the entire delivery process. It can match the order with a suitable delivery man and send a tracking
number to let the customer and the merchant know the delivery status of the order in real time. Fifth, the system
realizes the online payment function. Once the food is delivered, the system will automatically deduct the effective
account provided by the customer, and will pay the merchant, the distributor, and the platform. Several techniques
for system analysis, such as process models, logical models, entity relationship diagrams, and Unified Modelling
Language, are used in this report for showing how the Ele.me food delivery system realizes the above four
functions from various angles.
Business Analysis of the Ele.me System
Page 3 of 38
Business Analysis of the Ele.me System
Page 4 of 38
Section 1 – Introduction
1.1 Organisation’s background and overall system
Ele.me" is a catering O2O platform that provides integrated operation solutions for catering merchants in China.
This comprehensive food delivery system achieves multiple functions. First, it allows restaurants register on the
platform to display their basic information, such as picture information, menus, and the map to show their
location. Second, the customers use this system to make a food order. In addition, if the customer chooses to
become a member, there provide an independent membership centre management after the registration. Third,
the deliverers use this system to take orders. Once they receive an order, they need pick up the order from the
restaurant and delivery to the customer.
This report will conduct a system analysis of the Ele.me food delivery system. The first section is going to
introduce the whole system and organizational background, as well as the reasons for choosing this system. In
the second section, the system scope, components, constraints, and interrelationships will be discussed. In the
third part, the requirements are collected and will be further analysed. Section 4 will further explain the
corresponding DFDs, logical models, and Enhanced ERD. Section 5 will show and illustrate the UML models of
this system. The Reflection and conclusion will be discussed in Sections 6.
1.2 Rationale
Nowadays, with the development of Internet technology, more and more people choose the door-to-door food
delivery service. What’s more, the COVID-19 pandemic has catalysed this service technology since it facilitates
people enjoy the food without leaving home. I chose to study the food delivery system for several reasons. First,
I read a few social news about the unprotected rights of food deliverers in China, so I want to learn about the
relationship between deliverers and the platform and businesses through deeper study of this system. Secondly,
I have seen many food-safety issues happened. In this system, how the qualifications of merchants are
evaluated and monitored. Finally, I found that in China, more and more small and medium-sized catering
businesses prefer to register on Ele.me platforms to support their delivery services. Therefore, I want to further
explore whether merchants can really benefit from using this system?
Business Analysis of the Ele.me System
Page 5 of 38
Section 2 – System overview
2.1 Systems Diagram
2.2 Scope
2.2.1 High level system functions
The major functions of the system include:
1) In order to ensure the food security, the system evaluates and monitor the qualifications of the
merchants who would like to register on the Ele.me platform, as well as the qualifications of the
deliverer by checking their resumes and health certificate.
2) Allows the customers to submit an order and facilitates the restaurants to receive the order.
3) Allow the deliverers to take orders by obtaining both restaurants and customers address and contact
number, and then delivery the food.
Business Analysis of the Ele.me System
Page 6 of 38
4) The system conducts automatic deductions for consumers, and distribute the profits to the merchants,
the delivery drivers, and the platform in proportion.
2.2.2 System Environment
As shown in the diagram, the area outside the logical boundary is the environment which contains customers,
catering businesses, delivery drivers, Ele.me platform company, banks, and the administration for market
regulation who is responsible to authenticates and documents their qualifications.
2.2.3 Purpose
The purpose of Ele.me food delivery system is to provide door-to-door service which could connect the carting
businesses and customers directly and convivence both.
2.2.4 Input
• Restaurant’s details (address; contact number; bank account details; available delivery time and
destinations; status of food items etc.)
• Customer’s details (name; delivery address; contact number; bank account details; selection of food
items; preferred delivery time, notes etc.)
• Deliverer’s detail (name; contact number; bank account details; health certificate etc.)
• Restaurant’s application for registration
• Administration’s evaluation report for the application
• Platform company’s evaluation report for the application
• The confirmation by deliverer of taking an order.
• The payment status reported by the Banks
2.2.5 Output
• Approval notifications of the application
• Order details (food items info; delivery time; delivery address etc.)
• The messages of order’s tracking number
• Payment details
• Payment status notifications (to customers, businesses, platform, and banks)
2.2.6 Interfaces
The interfaces for Ele.me food delivery system is where collects the inputs and generates the outputs.
For customers, the interface is the Ele.me app which can be downloaded in the app store. For
businesses/ delivery driver/ bank/ Ele.me company/ Administration of market regulation/, the interface is
computers or other mobile devices.
Business Analysis of the Ele.me System
Page 7 of 38
2.2.7 Boundaries
As shown in the above diagram, the boundary of Ele.me food delivery system is represented by the
dotted line which identifies the internal environment and the external environment of the system.
2.3 Components
This report is going to document all the components inside the boundary, which are shown below:
• Component 1- Application approval system: through the system, businesses could submit the application
which contains basic information and qualifications; administration for market regulation could review the
applications and examine their qualifications. According to the report that uploaded by administration, the
Ele.me platform will finally confirm their registration.
• Component 2- Oder process system: through the system, customers could select the restaurant and the food
items. Once they confirm to submit the order and complete the virtual paying, the system will generate
notifications involving relevant order information, and then transfer to the restaurants, delivery system, and
payment system.
• Component 3- Delivery system: Once receives the order information transferred form order system, the
delivery system would match a deliverer for the order. When the deliverer confirms to take the order, the
system generates the tracking number of the order, and send it to customers.
• Component 4- Payment system: When the consumer checks the goods correctly and confirms receipt, the
system will send a reminder to the customer's bank account based on the information transferred form order
system and deduct the money. At the same time, the transaction amount will be transferred to the bank
account of the business, the deliverer, and the platform enterprise according to the proportion agreed in the
contract.
2.4 Interrelationships
1) Since only businesses that pass the qualification evaluation can successfully register on the platform. In the
order system, the platform only provides restaurants that have been screened by the application approval
system.
2) Once the order process completed, the delivery process will match the delivery driver for the order and
generate relevant order information according to the information provided by order process.
3) Third, although the customer has completed the virtual payment operation during the order process, the
actual payment process does not begin until the delivery process is completed.
Business Analysis of the Ele.me System
Page 8 of 38
2.5 Constraints
2.5.1 Internal
• The architecture of the system: since the system architecture is based on the internet, therefore, it
cannot run without stable internet support.
• Capabilities of the app design, big data technology, and the IOT technology: the technologies
which are intended to be applied in developing and implementing this system will affect its
performance as well.
• Each stage of developing the system: The approach of development would affect the success of
delivering the system.
2.5.2 External
• Skills availability of users: if the users input the wrong information into the system such as
unclear address, and incorrect contact number etc.
• Policies, laws, and government regulations: the restaurants without offline stores and business
licences cannot register on the Ele.me platform; and deliverers without health certificate cannot
take the order.
• Other information systems it interacts: the system it interacts with most often is Alipay system
which is the popular payment system used among Ele.me users, if this system fails, the
subsystem of payment will fail as well. Another instance is the GPS system, if the food delivery
system has the function of displaying the real-time position of the deliverer to figure out how long
it will take to receive the order. If the GPS system fails, this function will fail as well.
2.6 Negative and positive feedback
2.6.1 Negative Feedback
The number of orders that generate from the system has been found to be flat for a long time and showing a
downward trend. Coupons and reduced delivery fee activities can increase order volume to higher normal levels.
2.6.2 Positive Feedback
The system output of application approval becomes stricter and more formal due to the administration of market
regulation ask the businesses submit more comprehensive information to state their qualifications.
Business Analysis of the Ele.me System
Page 9 of 38
Section 3 – Requirements Analysis
3.1 Requirements gathering
In order to gather requirements, the following sources of information were relied upon document
analysis, surveys, and interviews.
3.1.1 Document Analysis
Through conducting the document analysis, first we can find the problems with the existing systems such as
Uber Eats and Menulog. Second, we can clearly know key individual’s name. Third, the reasons for current
system design and the rules for processing the data can be referenced as well.
3.1.2 Surveys
This is an effective and time saving method. Through two kinds of questionnaire designed for the customer and
catering businesses, the general requirements from them have been collected successfully.
3.1.3 Interviews
This method of semi-structured interviews with random sample is used for determining the requirements of the
deliverer. It is a useful way to obtain unexpected materials from the interviewed delivery drivers.
3.2 Requirement identification
No Requirement identified User Functional/
Non-functional
Level of
importance
1 Allow customer create account and log in and provide
their basic information.
Customer Functional Mandatory
2 Provide the basic information of restaurant such as
address, pictures of dishes, comments history, ratings.
Customer Functional Mandatory
3 Selecting the food items and changing the item
amount.
Customer Functional Mandatory
4 Allow customer to choose the delivery time within the
available time.
Customer Functional Mandatory
5 Add notes attached to the order, such as telling the
restaurant what ingredients they are allergic to; and
notifying the deliverer not to knock the door etc.
Customer Functional Mandatory
6 Allow tracking the order. Customer Functional Mandatory
7 Allow checking the real-time position of the deliverer to Customer Functional Desirable
Business Analysis of the Ele.me System
Page 10 of 38
know how long it will take to receive the order.
8 Allow feedback, comments, and ratings the
restaurants.
Customer Functional Desirable
9 Allow feedback, comments, and ratings the deliverer. Customer Functional Desirable
10 Allow collection of favourite restaurants. Customer Functional Frill
11 Allow self-design of the home page, such as adding
restaurants that order frequently.
Customer Functional Frill
12 Obtain coupons on the platform. Customer Functional Desirable
13 Allow submit application through the system and
register on the platform along with uploading basic
information.
Restaurant Functional Mandatory
14 Allow receiving the order information in the real time. Restaurant Functional Mandatory
15 Allow processing of a large number of orders at the
same time.
Restaurant Non-functional Mandatory
16 Contacting the deliverer who pick up the food items. Restaurant Functional Mandatory
17 Receiving the payment notification. Restaurant Functional Mandatory
18 Allow marketing activities on the platform. Restaurant Functional Desirable
19 Communicating with customers directly through the
system.
Restaurant Functional Desirable
20 Allow submitting the application and becoming the
deliverer of the Ele.me platform.
Deliverer Functional Mandatory
21 Receiving the order information. Deliverer Functional Mandatory
22 Send notifications of order tracking number when food
items are picked up.
Deliverer Functional Mandatory
23 Receiving the payment notifications once they finished
the order.
Deliverer Functional Mandatory
24 Allow accepting the tips from the customer if they
perform good.
Deliverer Functional Desirable
25 Receiving the payment information. Bank Functional Mandatory
26 Sending the payment status notification. Bank Functional Mandatory
27 Allow storing data of registered users Platform Functional Mandatory
28 Allow contracting with evaluated users Platform Functional Desirable
29 Offering membership account management. Platform Functional Desirable
30 The system could respond within 0.5 second. Platform Non-functional Desirable
31 The system will provide users with round-the-clock Platform Non-functional Desirable
Business Analysis of the Ele.me System
Page 11 of 38
service except the maintenance time.
32 The system could update data to the cloud in real time. Platform Non-functional Desirable
33 The system is user friendly. Platform Non-functional Desirable
34 Allow receiving and reviewing the application. Administration Functional Mandatory
35 Allow uploading the approval advice report. Administration Functional Mandatory
3.3 Matching system functions with requirements
System functions Requirement
1. Evaluate the qualifications of
users
• Allow submit application through the system and register on the
platform along with uploading basic information.
• Allow submitting the application and becoming the deliverer of
the Ele.me platform.
• Allow administration to receive and review the application.
• Allow administration to upload the approval advice report.
• The system is user friendly.
2. Create accounts with details of
registered users
• Allow customer create account and log in and provide their basic
information.
• Allow restaurant to register on the platform along with uploading
basic information.
• Allow deliverer to register on the platform.
• Allow storing data of registered users
• The system is user friendly.
3. Generate and process the
orders
• Allow customer create account and log in and provide their basic
information.
• Allow customers to select the food items and to change the item
amount.
• Allow customer to choose the delivery time within the available
time.
• Allow customers to add notes attached to the order
• Allow restaurants receiving the order information in the real time.
• The system is user friendly.
Business Analysis of the Ele.me System
Page 12 of 38
4. Execute delivery process • Allow the restaurant to contact the deliverer who pick up the
food items.
• Allow deliverer to receive the order information.
• Allow deliverer to send notifications of order tracking number
when food items are picked up.
• Allow customer to receive the track number and track the order.
• Allow customer to confirm that the food item is delivered.
• The system is user friendly.
5. Execute payment operation • Generating the payment information of each order.
• Allow Bank to receive the payment information.
• Allow bank to send the payment status notification.
• Allow relevant users to receive the payment status notification.
• The system is user friendly.
Business Analysis of the Ele.me System
Page 13 of 38
Section 4 - Traditional models
4.1 Process and Logic Model
i. Narrative for DFDs (Level 0)
First of all, the food delivery system takes the responsibility of evaluating the qualifications of the restaurants and
the deliverers, in order to ensuring the food safety. If they want to register on the Ele.me platform, they need to
submit the application through the system. Then the system will send the application to the Administration of
market regulation, a third-party organization, to check the validity of the applications and give corresponding
advice report. Then the system will send the applications which has already been adviced by third-party
organization to the Ele.me platform for further confirmation and will files the report into advice report data.
Ele.me could reference to the advice report stored in the system and finally give an approval opinion of the
application. And the applicants will receive the notification of approval opinion through the system. Finally, the
system will separately file the applications attached with approval opinion into deliverer application data store
and restaurant application store.
Secondly, the user can create their account on the platform based on their role. In particular, the restaurant and
the deliverer need have the approved opinion on their application, otherwise they cannot create the account
since they didn’t pass the qualification evaluation. When the user enters the details, the system will automatically
generate an account. In addition, user details are archived into customer details, delivery man details, and
restaurant data stores respectively.
Thirdly, once customer finished selecting food item on the system, the system begins the generate order
process. Restaurant will receive the relevant order information and check the inventory level of the food item
requested by the order in order to think whether accept the order. Once the system receives the acceptance
form the restaurant, it will update the order status by “accepted” and it will retrieve address and contact details
form customer details and restaurant details for collecting the shipping information. Then the system generates
the order with complete delivery information, send the receipt to customer, and save the order details into order
details data store.
Fourthly, since only the order accepted by restaurant can generate the delivery process and the restaurant need
to send the request for matching deliverer for the order. The system should retrieve the order status data store to
confirm the orders has been accepted by restaurant first. Then retrieve the details of these confirmed order from
the order details data store. The system can automatically send match request to deliverers who are appropriate
according to the shipping information of the order. The deliverers need to confirm whether they are willing to
deliver the order. Once the system receives one confirmation form the deliverer, it will collect the deliverer
information from the deliverer details data store, which used for identifying the deliverer and contacting with him.
Business Analysis of the Ele.me System
Page 14 of 38
What’s more, each order will be assigned with a unique track number which will be sent to customer and
restaurant through the system. In addition, the order details data store will be updated with the deliverer
information and the unique order track number, and the order status data store will be updated by “delivering”
status.
Finally, this system is responsible for paying the relevant stakeholders who are the customer, the deliverer, and
the restaurant involved in the order. When the food items requested by the order have been delivered
successfully, the system will execute a payment for this order. The system checks the status from retrieving the
order status data store and collect the payment information of the orders which status is “delivered” from
retrieving the order details data store. Then the system will send the payment information to the bank. When the
bank finished the pay run in the reality, it will send payment report and the notification s of payment status to the
system. And the system should send the payment notifications to the customer, the deliverer, and the restaurant
respectively. In the end, the payment status data store will be updated, and the payment report will be filed away
into the Payment report file.
Business Analysis of the Ele.me System
Page 15 of 38
ii. The context level DFD of the process described above
Business Analysis of the Ele.me System
Page 16 of 38
iii. The level 0 DFD of the process described above
Business Analysis of the Ele.me System
Page 17 of 38
iv. The level 1 DFDs of the processes described above and corresponding logic models
Level 1 DFD & Logic Models for Process 1
Logic model for process 1.1
Get application from applicants
Get applicant’s information from application detail
Display application
Logic model for process 1.2
IF user type is Restaruarnt THEN
Generate restaurant application
ELSE
IF user type is Deliverer THEN
Generate deliverer application
ELSE
Show error alert
END IF
END IF
Logic model for process 1.3
Receive the restaurant application
Send to Administration for market regulation for reviewing
Receive approval advice report form Administration for market regulation
Files Advice report into data store
Logic model for process 1.4
Receive the updated restaurant appication with advice report or deliverer application
Send to Ele.me platform company for reviewing
Receive comfirmation from Ele.me platform company
Generate notification of approval opinion
IF user type is Restaruarnt THEN
Send notification to restaurant
ELSE
IF user type is Deliverer THEN
Send notification to deliverer
Business Analysis of the Ele.me System
Page 18 of 38
ELSE
Show error alert
END IF
END IF
Logic model for process 1.5
Get application with approval opinion
IF user type is Restaruarnt THEN
Files application into restaurant application data store
ELSE
IF user type is Deliverer THEN
Files application into deliverer application data store
ELSE
Show error alert
END IF
END IF
Level 1 DFD & Logic Models for Process 2
Logic model for process 2.1
Receive the user details
Read user type
IF user type is Restaruarnt or Deliverer THEN
Request qualification check
ELSE
IF user type is Customer THEN
Request creating account
END IF
END IF
Logic model for process 2.2
IF user type is Restaruarnt THEN
Retrieve restaurant application data
ELSE
IF user type is Deliverer THEN
Retrieve deliverer application data
END IF
END IF
Business Analysis of the Ele.me System
Page 19 of 38
Confirm the approval opinion of the application
IF the approval opinion is approved THEN
Approve to create account
ELSE
Reject create account
END IF
Logic model for process 2.3
Get approved user
IF user type is Restaruarnt THEN
Generate restaurant account
ELSE
IF user type is Deliverer THEN
Generate deliverer account
ELSE
IF user type is Customer THEN
Generate deliverer account
END IF
END IF
END IF
Logic model for process 2.4
IF Restaruarnt account THEN
Files account detail into restaurant details data store
ELSE
IF Deliverer account THEN
Files account detail into deliverer details data store
ELSE
IF Cutomer account THEN
Files account detail into customer details data store
END IF
END IF
END IF
Level 1 DFD & Logic Models for Process 3
Business Analysis of the Ele.me System
Page 20 of 38
Logic model for process 3.1
Get the customer order from customers
Get the raw order detail
Logic model for process 3.2
Get the order detail
Translate to restaurant order format
Send the order detail in restaurant order format to restaurant for reviewing
Logic model for process 3.3
Receive order acceptance form the restaurant
Receive the order detail
Retrieve delivery information form restaurant detail data store
Retrieve delivery information form cutomer detail data store
Generate order detail
Updates order detail data store with adding delivery information
Updates order status data store
Logic model for process 3.4
Receive the order detail with delivery information
Translate the updated order detail into receipt format
Send the receipt to the customer
Level 1 DFD & Logic Models for Process 4
Business Analysis of the Ele.me System
Page 21 of 38
Logic model for process 4.1
Receive match deliverer request of the order form restaurant
Retrieve order status from the Order Status data store
IF the order status is accepted by restaurant THEN
Input order details
END IF
Logic model for process 4.2
Receive the confirmed order information
Send the match request to the deliverers
Receive a confirmation of acceptance from a deliverer
Retrieve deliverer details from the Deliverer Details data store
Logic model for process 4.3
IF the order has been matched a delivery successfully THEN
Send the order information to the deliverer
END IF
Receive the confirmation of beginning to pick up the order from deliverer
Display the deliverying status of the order
Update the Order status data store
Logic model for process 4.4
IF the order has been picked up successfully THEN
Generate a track number for the order
END IF
Send the track number to the customer
Send the track number to the restaurant
Update the Oder Details data store with adding track number
Display the order status is deliverying
Update the Order Status data store
Logic model for process 4.5
Business Analysis of the Ele.me System
Page 22 of 38
Level 1 DFD & Logic Models for Process 5
Logic model for process 5.1
Retrieve Order status form Order status data store
IF order status is finished delivery THEN
Collect the finished order details
END IF
Logic model for process 5.2
Retrieve payment information form Order details data store
Compute the final payment information according to the raw payment information
Display the final payment information
Logic model for process 5.3
Receive the final payment information
Send the final payment information to the Bank
Receive the payment status notification from Bank
Files the Payment Status data store
Logic model for process 5.4
Retrieve Payment Status form Payment Status data store
Send the Payment status notification to Customer
Send the Payment status notification to Restaurant
Send the Payment status notification to Delivery
Logic model for process 5.5
Receive the payment report form Bank
File the payment report into Payment Report data store
Business Analysis of the Ele.me System
Page 23 of 38
4.2 Entity Relationship (ER) Diagram
i. Narrative for Entity Relationship Model
In this ER model as shown in the part (ii), the user of the Ele.me food delivery system has three types which are
customer, deliverer, and restaurant. Every user has a unique user ID, and they are asked to offer an available
payment method. On the system, every user can create accounts, and each account includes a unique account
ID, password, profile image, and the role which identify the purpose of the account. For instance, a restaurant
account only be used for receiving the order or uploading their menu etc. It cannot be used for placing an order.
To control the food safety issue, some of the user (restaurants and deliverers) need to submit application for
registration. All applications have a unique application ID, the date of submit, and the attachments. In detail, the
deliverer application contains deliverer’s resume and the health certificate. This type of applicat ion will be
evaluated and approved by Ele.me platform company only. While the restaurant application should be evaluated
by the third-party organization first to check the validity of the qualifications involved in the application and
approved by the Ele.me company. All approved applications will obtain the approve number.
The order is placed by the customer. Each order has a unique order ID, status, the date of generate, notes
attached, asked delivery time, pick-up information, and arrive information. The order has the food items selected
on the system. Each food item is identified by name, amount, and notes. The food items will be made by the
restaurant and be delivered by the deliverer. In order to ensuring the success of the shipping of the order, the
customer and the restaurant should provide the name, address, and contact number; and the deliverer should
provide the name and contact number. What’s more, in the delivery process, every order will be assigned with a
unique track number.
Finally, each order has a payment which has the payment ID, date of generate, the bank which implement the
pay run, the amount of payment need to give to relevant user, corresponding order ID, and the person who
conduct the real payment.
Business Analysis of the Ele.me System
Page 24 of 38
ii. ER diagram
Assumptions
• We assume that for each order it only have one unique customer.
• We assume that customers can make many orders, and not every customer on the system will make an
order.
• We assume that one customer could only make one order of only one selected restaurant one time. If the
customers want to order other food items form another restaurant, they need to place another order.
• We assume that one order must have at least one food item or the order cannot be generated.
• We assume that only when the delivery process begins, the track number of the order can be generated.
• We assume that the subclass of the user is overlapped, because a deliverer may also be a customer on the
Business Analysis of the Ele.me System
Page 25 of 38
system. However, if the deliverer wants to transfer its role to customer, it is necessary to login the customer
account. Using the deliverer account cannot order on the system.
• We assume that as the user of the system, they must have accounts, and can have different accounts.
• We assume that only the restaurants and the deliverers need to submit the application. And the subclass of
the application is disjoint.
• We assume that for the restaurants and the deliverer, get the approval of the application is the pre-
condition of creating the account.
• We assume that only the restaurant application needs to be evaluated by the third-party organization.
• The user ID, application ID, payment ID, account ID, order ID are created automatically by the system.
• We assume that the user ID is as same as the account ID.
• In order to identifying the organization on the system better, we assume that the organizations, that
participate in the evaluation stage, will be assigned with a unique organization ID number.
• We assume the address of customer is a repeating group, while the address of restaurant should only have
one constant value.
Business Analysis of the Ele.me System
Page 26 of 38
4.3 ER diagram dictionary
Business Analysis of the Ele.me System
Page 27 of 38
Business Analysis of the Ele.me System
Page 28 of 38
Business Analysis of the Ele.me System
Page 29 of 38
Section 5 – Modern Analysis (UML Models)
5.1 Use case diagram
Business Analysis of the Ele.me System
Page 30 of 38
5.2 Descriptions for each use case
Use case name: Evaluate qualification
Actor(s): Restaurant, Deliverer, Administration for market regulation, Ele.me
Description: This use case allows restaurant and deliverer to submit the applications for
registration. Their qualifications will be evaluated by Administration for market regulation
and Ele.me.
Steps: Information required [produced]:
Applicant submits the application [Application No]
If applicant is a restaurant, send the
application to the Administration for market
regulation for reviewing. And it will give the
advice report
[Advice Report No]
Ele.me will give restaurant the approval
opinion of the application through reviewing
the application and the advice report.
Application No and Advice Report No
[Approval opinion]
If applicant is a deliverer, send the application
to the Ele.me for reviewing.
Ele.me will give deliverer the approval
opinion of the application through reviewing
the application.
Application No
[Approval opinion]
Use case name: Create account
Actor(s): Customer, Restaurant, Deliverer
Description: This use case allows the customer, restaurant, and the deliverer to create
account for different purpose.
Steps: Information required [produced]:
If the user plays the role of customer and
want to create account
Customer detail (name, address, contact
number, payment method)
Create customer account for the user [Account ID]
If the user plays the role of deliverer and
requests to create account
Deliverer details (name, contact number,
payment method), Approval opinion
If the approval opinion is disapproving state,
reject request and quit.
Create deliverer account for the user [Account ID]
If the user plays the role of restaurant and
requests to create account
Restaurant details (name, address,
contact number, payment method),
Approval opinion
If the approval opinion is disapproving state,
reject request and quit.
Create restaurant account for the user [Account ID]
Business Analysis of the Ele.me System
Page 31 of 38
Use case name: Generate and process the order
Actor(s): Customer, Restaurant
Description: This use case allows customers to place orders on the system and allows
restaurants process the orders.
Steps: Information required [produced]:
The Customer select and fill the order details Order details (food item type, amount,
notes, delivery time, shipping address,
contact number)
Generate the order and send the order
details to the restaurant
[Order No]
If restaurant reject to accept the order, then
cancel the order, and quit.
If restaurant accept the order, then generate
the receipt, and send to customer
[Receipt]
Initiate “Execute delivery process” use case
Use case name: Execute delivery process
Actor(s): Customer, Restaurant, Deliverer
Description: This use case allows deliverer to ship the order. By picking up food items
from restaurant and delivering them to customer.
Steps: Information required [produced]:
Restaurant send the match deliverer request
for the order.
Order No
Generate delivery request and send to
possible deliverers.
Order details
If no deliverer accepts the delivery request,
then cancel the order and quit.
If the deliverer accepts the deliverer request,
then add deliverer details to the order and
generate the track number which will send to
the customer and restaurant.
Deliverer details
[Track No]
If the deliverer delivered the order and update
the order status of the order detail, then
initiate “Execute payment process” use case
Business Analysis of the Ele.me System
Page 32 of 38
Use case name: Execute payment process
Actor(s): Bank, Customer, Restaurant, Deliverer, Ele.me company
Description: This use case allows the customer to pay the order; allows the restaurant,
the deliverer, and the company to get paid; allows the Bank to help the system finish the
payment in the reality.
Steps: Information required [produced]:
Bank will receive the payment request for the
order
Order details, Customer details
(payment method), Deliverer details
(payment method), Restaurant details
(payment method)
Bank implement the actual payment and
upload the Payment report
Payment Report
Generate the Payment No and Payment
status for the order
[Payment No] [Payment Status]
Send the Payment No and Status to
customer
Payment No, Payment Status, Account
ID
Send the Payment No and Status to deliverer Payment No, Payment Status, Account
ID
Send the Payment No and Status to
restaurant
Payment No, Payment Status, Account
ID
Business Analysis of the Ele.me System
Page 33 of 38
5.3 Class diagram
Business Analysis of the Ele.me System
Page 34 of 38
5.4 Sequence and/or Activity Diagram
Use Case 1: Evaluate qualification
Use Case 2: Create Account
Business Analysis of the Ele.me System
Page 35 of 38
Use Case 3: Generate and process order
Use Case 4: Execute delivery process
Use Case 5: Execute payment process
Business Analysis of the Ele.me System
Page 36 of 38
5.5 State machine
Business Analysis of the Ele.me System
Page 37 of 38
Section 6 – Conclusion & Reflection
This report conducts a comprehensive analysis of the Ele.me food delivery system which is the most popular
system used in China. In order to get deeper understanding of this system, the report conduct a requirements
analysis to identifies the functions that a food delivery system should achieve in response to these requirements.
Furthermore, DFD, Logical models, EER diagrams, and UML are used for analysing how can the Ele.me system
realizes five major functions which are evaluating qualifications, creating account, generating, and processing
order, executing delivery process, and executing payment process.
Through finishing this assignment, first, I have a better understanding of this food delivery system through
research how the system interacts with external environment, as well as how the things within the system
interact with each other and work together. In addition, when using different system analysis tools, I find that
each one gives a different perspective to explain the system, and they have similarities and differences. More
importantly, I found that each stage was linked and show the recursive relationship. For example, when
analysing the system through UML, I kept going back to add and modify the previous diagrams as I progressed.
This shows that the system design is not accomplished in one time, the design results will be constantly
improved during the design process.
Business Analysis of the Ele.me System
Page 38 of 38
Section 7 – References
Shah, N., Shah, H., Sheth, S., Chauhan, R. and Desai, C., 2021. Local Food Delivery System. SSRN Electronic
Journal.
Technology and Operations Management. 2021. Ele.me, Digitizing the food delivery service in China - Technology
and Operations Management. [online] Available at:digitizing-the-food-delivery-service-in-china/> [Accessed 10 November 2021].
Final Report
Business Analysis of the Food Delivery System
-Ele.me
Business Analysis of the Ele.me System
Page 2 of 38
Executive summary
Nowadays, food delivery service is more and more popular. Consumers are willing to pay additional delivery fees
to enjoy the service of delivering food to their door. In addition, the coronavirus pandemic has catalysed this trend,
and this service have facilitated people's lives. In China, the food delivery service is very mature, and the Ele.me
platform is one of the most popular food delivery systems. Through the requirements analysis, we understand the
expectations of relevant stakeholders for the food delivery system. To respond to these expectations, the Ele.me
food delivery system mainly implements four major functions. First, in order to effectively control food safety issues,
this system must be able to verify the qualifications of merchants and deliverers. If the merchant does not have a
legal operating permit or the delivery staff is unhealthy, it will affect the quality of delivery service. Second, this
system allows users who play different roles to create account for different purpose. For example, the deliverer
account mainly used for allowing deliverers to receive match request and track the delivery process, while the
customer account mainly used for allowing customers to place orders. Third, this system must implement online
order placement and order processing functions. This function allows consumers and merchants to achieve
barrier-free remote communication by transmitting detailed information about the order. Fourth, this system
guarantees the entire delivery process. It can match the order with a suitable delivery man and send a tracking
number to let the customer and the merchant know the delivery status of the order in real time. Fifth, the system
realizes the online payment function. Once the food is delivered, the system will automatically deduct the effective
account provided by the customer, and will pay the merchant, the distributor, and the platform. Several techniques
for system analysis, such as process models, logical models, entity relationship diagrams, and Unified Modelling
Language, are used in this report for showing how the Ele.me food delivery system realizes the above four
functions from various angles.
Business Analysis of the Ele.me System
Page 3 of 38
Business Analysis of the Ele.me System
Page 4 of 38
Section 1 – Introduction
1.1 Organisation’s background and overall system
Ele.me" is a catering O2O platform that provides integrated operation solutions for catering merchants in China.
This comprehensive food delivery system achieves multiple functions. First, it allows restaurants register on the
platform to display their basic information, such as picture information, menus, and the map to show their
location. Second, the customers use this system to make a food order. In addition, if the customer chooses to
become a member, there provide an independent membership centre management after the registration. Third,
the deliverers use this system to take orders. Once they receive an order, they need pick up the order from the
restaurant and delivery to the customer.
This report will conduct a system analysis of the Ele.me food delivery system. The first section is going to
introduce the whole system and organizational background, as well as the reasons for choosing this system. In
the second section, the system scope, components, constraints, and interrelationships will be discussed. In the
third part, the requirements are collected and will be further analysed. Section 4 will further explain the
corresponding DFDs, logical models, and Enhanced ERD. Section 5 will show and illustrate the UML models of
this system. The Reflection and conclusion will be discussed in Sections 6.
1.2 Rationale
Nowadays, with the development of Internet technology, more and more people choose the door-to-door food
delivery service. What’s more, the COVID-19 pandemic has catalysed this service technology since it facilitates
people enjoy the food without leaving home. I chose to study the food delivery system for several reasons. First,
I read a few social news about the unprotected rights of food deliverers in China, so I want to learn about the
relationship between deliverers and the platform and businesses through deeper study of this system. Secondly,
I have seen many food-safety issues happened. In this system, how the qualifications of merchants are
evaluated and monitored. Finally, I found that in China, more and more small and medium-sized catering
businesses prefer to register on Ele.me platforms to support their delivery services. Therefore, I want to further
explore whether merchants can really benefit from using this system?
Business Analysis of the Ele.me System
Page 5 of 38
Section 2 – System overview
2.1 Systems Diagram
2.2 Scope
2.2.1 High level system functions
The major functions of the system include:
1) In order to ensure the food security, the system evaluates and monitor the qualifications of the
merchants who would like to register on the Ele.me platform, as well as the qualifications of the
deliverer by checking their resumes and health certificate.
2) Allows the customers to submit an order and facilitates the restaurants to receive the order.
3) Allow the deliverers to take orders by obtaining both restaurants and customers address and contact
number, and then delivery the food.
Business Analysis of the Ele.me System
Page 6 of 38
4) The system conducts automatic deductions for consumers, and distribute the profits to the merchants,
the delivery drivers, and the platform in proportion.
2.2.2 System Environment
As shown in the diagram, the area outside the logical boundary is the environment which contains customers,
catering businesses, delivery drivers, Ele.me platform company, banks, and the administration for market
regulation who is responsible to authenticates and documents their qualifications.
2.2.3 Purpose
The purpose of Ele.me food delivery system is to provide door-to-door service which could connect the carting
businesses and customers directly and convivence both.
2.2.4 Input
• Restaurant’s details (address; contact number; bank account details; available delivery time and
destinations; status of food items etc.)
• Customer’s details (name; delivery address; contact number; bank account details; selection of food
items; preferred delivery time, notes etc.)
• Deliverer’s detail (name; contact number; bank account details; health certificate etc.)
• Restaurant’s application for registration
• Administration’s evaluation report for the application
• Platform company’s evaluation report for the application
• The confirmation by deliverer of taking an order.
• The payment status reported by the Banks
2.2.5 Output
• Approval notifications of the application
• Order details (food items info; delivery time; delivery address etc.)
• The messages of order’s tracking number
• Payment details
• Payment status notifications (to customers, businesses, platform, and banks)
2.2.6 Interfaces
The interfaces for Ele.me food delivery system is where collects the inputs and generates the outputs.
For customers, the interface is the Ele.me app which can be downloaded in the app store. For
businesses/ delivery driver/ bank/ Ele.me company/ Administration of market regulation/, the interface is
computers or other mobile devices.
Business Analysis of the Ele.me System
Page 7 of 38
2.2.7 Boundaries
As shown in the above diagram, the boundary of Ele.me food delivery system is represented by the
dotted line which identifies the internal environment and the external environment of the system.
2.3 Components
This report is going to document all the components inside the boundary, which are shown below:
• Component 1- Application approval system: through the system, businesses could submit the application
which contains basic information and qualifications; administration for market regulation could review the
applications and examine their qualifications. According to the report that uploaded by administration, the
Ele.me platform will finally confirm their registration.
• Component 2- Oder process system: through the system, customers could select the restaurant and the food
items. Once they confirm to submit the order and complete the virtual paying, the system will generate
notifications involving relevant order information, and then transfer to the restaurants, delivery system, and
payment system.
• Component 3- Delivery system: Once receives the order information transferred form order system, the
delivery system would match a deliverer for the order. When the deliverer confirms to take the order, the
system generates the tracking number of the order, and send it to customers.
• Component 4- Payment system: When the consumer checks the goods correctly and confirms receipt, the
system will send a reminder to the customer's bank account based on the information transferred form order
system and deduct the money. At the same time, the transaction amount will be transferred to the bank
account of the business, the deliverer, and the platform enterprise according to the proportion agreed in the
contract.
2.4 Interrelationships
1) Since only businesses that pass the qualification evaluation can successfully register on the platform. In the
order system, the platform only provides restaurants that have been screened by the application approval
system.
2) Once the order process completed, the delivery process will match the delivery driver for the order and
generate relevant order information according to the information provided by order process.
3) Third, although the customer has completed the virtual payment operation during the order process, the
actual payment process does not begin until the delivery process is completed.
Business Analysis of the Ele.me System
Page 8 of 38
2.5 Constraints
2.5.1 Internal
• The architecture of the system: since the system architecture is based on the internet, therefore, it
cannot run without stable internet support.
• Capabilities of the app design, big data technology, and the IOT technology: the technologies
which are intended to be applied in developing and implementing this system will affect its
performance as well.
• Each stage of developing the system: The approach of development would affect the success of
delivering the system.
2.5.2 External
• Skills availability of users: if the users input the wrong information into the system such as
unclear address, and incorrect contact number etc.
• Policies, laws, and government regulations: the restaurants without offline stores and business
licences cannot register on the Ele.me platform; and deliverers without health certificate cannot
take the order.
• Other information systems it interacts: the system it interacts with most often is Alipay system
which is the popular payment system used among Ele.me users, if this system fails, the
subsystem of payment will fail as well. Another instance is the GPS system, if the food delivery
system has the function of displaying the real-time position of the deliverer to figure out how long
it will take to receive the order. If the GPS system fails, this function will fail as well.
2.6 Negative and positive feedback
2.6.1 Negative Feedback
The number of orders that generate from the system has been found to be flat for a long time and showing a
downward trend. Coupons and reduced delivery fee activities can increase order volume to higher normal levels.
2.6.2 Positive Feedback
The system output of application approval becomes stricter and more formal due to the administration of market
regulation ask the businesses submit more comprehensive information to state their qualifications.
Business Analysis of the Ele.me System
Page 9 of 38
Section 3 – Requirements Analysis
3.1 Requirements gathering
In order to gather requirements, the following sources of information were relied upon document
analysis, surveys, and interviews.
3.1.1 Document Analysis
Through conducting the document analysis, first we can find the problems with the existing systems such as
Uber Eats and Menulog. Second, we can clearly know key individual’s name. Third, the reasons for current
system design and the rules for processing the data can be referenced as well.
3.1.2 Surveys
This is an effective and time saving method. Through two kinds of questionnaire designed for the customer and
catering businesses, the general requirements from them have been collected successfully.
3.1.3 Interviews
This method of semi-structured interviews with random sample is used for determining the requirements of the
deliverer. It is a useful way to obtain unexpected materials from the interviewed delivery drivers.
3.2 Requirement identification
No Requirement identified User Functional/
Non-functional
Level of
importance
1 Allow customer create account and log in and provide
their basic information.
Customer Functional Mandatory
2 Provide the basic information of restaurant such as
address, pictures of dishes, comments history, ratings.
Customer Functional Mandatory
3 Selecting the food items and changing the item
amount.
Customer Functional Mandatory
4 Allow customer to choose the delivery time within the
available time.
Customer Functional Mandatory
5 Add notes attached to the order, such as telling the
restaurant what ingredients they are allergic to; and
notifying the deliverer not to knock the door etc.
Customer Functional Mandatory
6 Allow tracking the order. Customer Functional Mandatory
7 Allow checking the real-time position of the deliverer to Customer Functional Desirable
Business Analysis of the Ele.me System
Page 10 of 38
know how long it will take to receive the order.
8 Allow feedback, comments, and ratings the
restaurants.
Customer Functional Desirable
9 Allow feedback, comments, and ratings the deliverer. Customer Functional Desirable
10 Allow collection of favourite restaurants. Customer Functional Frill
11 Allow self-design of the home page, such as adding
restaurants that order frequently.
Customer Functional Frill
12 Obtain coupons on the platform. Customer Functional Desirable
13 Allow submit application through the system and
register on the platform along with uploading basic
information.
Restaurant Functional Mandatory
14 Allow receiving the order information in the real time. Restaurant Functional Mandatory
15 Allow processing of a large number of orders at the
same time.
Restaurant Non-functional Mandatory
16 Contacting the deliverer who pick up the food items. Restaurant Functional Mandatory
17 Receiving the payment notification. Restaurant Functional Mandatory
18 Allow marketing activities on the platform. Restaurant Functional Desirable
19 Communicating with customers directly through the
system.
Restaurant Functional Desirable
20 Allow submitting the application and becoming the
deliverer of the Ele.me platform.
Deliverer Functional Mandatory
21 Receiving the order information. Deliverer Functional Mandatory
22 Send notifications of order tracking number when food
items are picked up.
Deliverer Functional Mandatory
23 Receiving the payment notifications once they finished
the order.
Deliverer Functional Mandatory
24 Allow accepting the tips from the customer if they
perform good.
Deliverer Functional Desirable
25 Receiving the payment information. Bank Functional Mandatory
26 Sending the payment status notification. Bank Functional Mandatory
27 Allow storing data of registered users Platform Functional Mandatory
28 Allow contracting with evaluated users Platform Functional Desirable
29 Offering membership account management. Platform Functional Desirable
30 The system could respond within 0.5 second. Platform Non-functional Desirable
31 The system will provide users with round-the-clock Platform Non-functional Desirable
Business Analysis of the Ele.me System
Page 11 of 38
service except the maintenance time.
32 The system could update data to the cloud in real time. Platform Non-functional Desirable
33 The system is user friendly. Platform Non-functional Desirable
34 Allow receiving and reviewing the application. Administration Functional Mandatory
35 Allow uploading the approval advice report. Administration Functional Mandatory
3.3 Matching system functions with requirements
System functions Requirement
1. Evaluate the qualifications of
users
• Allow submit application through the system and register on the
platform along with uploading basic information.
• Allow submitting the application and becoming the deliverer of
the Ele.me platform.
• Allow administration to receive and review the application.
• Allow administration to upload the approval advice report.
• The system is user friendly.
2. Create accounts with details of
registered users
• Allow customer create account and log in and provide their basic
information.
• Allow restaurant to register on the platform along with uploading
basic information.
• Allow deliverer to register on the platform.
• Allow storing data of registered users
• The system is user friendly.
3. Generate and process the
orders
• Allow customer create account and log in and provide their basic
information.
• Allow customers to select the food items and to change the item
amount.
• Allow customer to choose the delivery time within the available
time.
• Allow customers to add notes attached to the order
• Allow restaurants receiving the order information in the real time.
• The system is user friendly.
Business Analysis of the Ele.me System
Page 12 of 38
4. Execute delivery process • Allow the restaurant to contact the deliverer who pick up the
food items.
• Allow deliverer to receive the order information.
• Allow deliverer to send notifications of order tracking number
when food items are picked up.
• Allow customer to receive the track number and track the order.
• Allow customer to confirm that the food item is delivered.
• The system is user friendly.
5. Execute payment operation • Generating the payment information of each order.
• Allow Bank to receive the payment information.
• Allow bank to send the payment status notification.
• Allow relevant users to receive the payment status notification.
• The system is user friendly.
Business Analysis of the Ele.me System
Page 13 of 38
Section 4 - Traditional models
4.1 Process and Logic Model
i. Narrative for DFDs (Level 0)
First of all, the food delivery system takes the responsibility of evaluating the qualifications of the restaurants and
the deliverers, in order to ensuring the food safety. If they want to register on the Ele.me platform, they need to
submit the application through the system. Then the system will send the application to the Administration of
market regulation, a third-party organization, to check the validity of the applications and give corresponding
advice report. Then the system will send the applications which has already been adviced by third-party
organization to the Ele.me platform for further confirmation and will files the report into advice report data.
Ele.me could reference to the advice report stored in the system and finally give an approval opinion of the
application. And the applicants will receive the notification of approval opinion through the system. Finally, the
system will separately file the applications attached with approval opinion into deliverer application data store
and restaurant application store.
Secondly, the user can create their account on the platform based on their role. In particular, the restaurant and
the deliverer need have the approved opinion on their application, otherwise they cannot create the account
since they didn’t pass the qualification evaluation. When the user enters the details, the system will automatically
generate an account. In addition, user details are archived into customer details, delivery man details, and
restaurant data stores respectively.
Thirdly, once customer finished selecting food item on the system, the system begins the generate order
process. Restaurant will receive the relevant order information and check the inventory level of the food item
requested by the order in order to think whether accept the order. Once the system receives the acceptance
form the restaurant, it will update the order status by “accepted” and it will retrieve address and contact details
form customer details and restaurant details for collecting the shipping information. Then the system generates
the order with complete delivery information, send the receipt to customer, and save the order details into order
details data store.
Fourthly, since only the order accepted by restaurant can generate the delivery process and the restaurant need
to send the request for matching deliverer for the order. The system should retrieve the order status data store to
confirm the orders has been accepted by restaurant first. Then retrieve the details of these confirmed order from
the order details data store. The system can automatically send match request to deliverers who are appropriate
according to the shipping information of the order. The deliverers need to confirm whether they are willing to
deliver the order. Once the system receives one confirmation form the deliverer, it will collect the deliverer
information from the deliverer details data store, which used for identifying the deliverer and contacting with him.
Business Analysis of the Ele.me System
Page 14 of 38
What’s more, each order will be assigned with a unique track number which will be sent to customer and
restaurant through the system. In addition, the order details data store will be updated with the deliverer
information and the unique order track number, and the order status data store will be updated by “delivering”
status.
Finally, this system is responsible for paying the relevant stakeholders who are the customer, the deliverer, and
the restaurant involved in the order. When the food items requested by the order have been delivered
successfully, the system will execute a payment for this order. The system checks the status from retrieving the
order status data store and collect the payment information of the orders which status is “delivered” from
retrieving the order details data store. Then the system will send the payment information to the bank. When the
bank finished the pay run in the reality, it will send payment report and the notification s of payment status to the
system. And the system should send the payment notifications to the customer, the deliverer, and the restaurant
respectively. In the end, the payment status data store will be updated, and the payment report will be filed away
into the Payment report file.
Business Analysis of the Ele.me System
Page 15 of 38
ii. The context level DFD of the process described above
Business Analysis of the Ele.me System
Page 16 of 38
iii. The level 0 DFD of the process described above
Business Analysis of the Ele.me System
Page 17 of 38
iv. The level 1 DFDs of the processes described above and corresponding logic models
Level 1 DFD & Logic Models for Process 1
Logic model for process 1.1
Get application from applicants
Get applicant’s information from application detail
Display application
Logic model for process 1.2
IF user type is Restaruarnt THEN
Generate restaurant application
ELSE
IF user type is Deliverer THEN
Generate deliverer application
ELSE
Show error alert
END IF
END IF
Logic model for process 1.3
Receive the restaurant application
Send to Administration for market regulation for reviewing
Receive approval advice report form Administration for market regulation
Files Advice report into data store
Logic model for process 1.4
Receive the updated restaurant appication with advice report or deliverer application
Send to Ele.me platform company for reviewing
Receive comfirmation from Ele.me platform company
Generate notification of approval opinion
IF user type is Restaruarnt THEN
Send notification to restaurant
ELSE
IF user type is Deliverer THEN
Send notification to deliverer
Business Analysis of the Ele.me System
Page 18 of 38
ELSE
Show error alert
END IF
END IF
Logic model for process 1.5
Get application with approval opinion
IF user type is Restaruarnt THEN
Files application into restaurant application data store
ELSE
IF user type is Deliverer THEN
Files application into deliverer application data store
ELSE
Show error alert
END IF
END IF
Level 1 DFD & Logic Models for Process 2
Logic model for process 2.1
Receive the user details
Read user type
IF user type is Restaruarnt or Deliverer THEN
Request qualification check
ELSE
IF user type is Customer THEN
Request creating account
END IF
END IF
Logic model for process 2.2
IF user type is Restaruarnt THEN
Retrieve restaurant application data
ELSE
IF user type is Deliverer THEN
Retrieve deliverer application data
END IF
END IF
Business Analysis of the Ele.me System
Page 19 of 38
Confirm the approval opinion of the application
IF the approval opinion is approved THEN
Approve to create account
ELSE
Reject create account
END IF
Logic model for process 2.3
Get approved user
IF user type is Restaruarnt THEN
Generate restaurant account
ELSE
IF user type is Deliverer THEN
Generate deliverer account
ELSE
IF user type is Customer THEN
Generate deliverer account
END IF
END IF
END IF
Logic model for process 2.4
IF Restaruarnt account THEN
Files account detail into restaurant details data store
ELSE
IF Deliverer account THEN
Files account detail into deliverer details data store
ELSE
IF Cutomer account THEN
Files account detail into customer details data store
END IF
END IF
END IF
Level 1 DFD & Logic Models for Process 3
Business Analysis of the Ele.me System
Page 20 of 38
Logic model for process 3.1
Get the customer order from customers
Get the raw order detail
Logic model for process 3.2
Get the order detail
Translate to restaurant order format
Send the order detail in restaurant order format to restaurant for reviewing
Logic model for process 3.3
Receive order acceptance form the restaurant
Receive the order detail
Retrieve delivery information form restaurant detail data store
Retrieve delivery information form cutomer detail data store
Generate order detail
Updates order detail data store with adding delivery information
Updates order status data store
Logic model for process 3.4
Receive the order detail with delivery information
Translate the updated order detail into receipt format
Send the receipt to the customer
Level 1 DFD & Logic Models for Process 4
Business Analysis of the Ele.me System
Page 21 of 38
Logic model for process 4.1
Receive match deliverer request of the order form restaurant
Retrieve order status from the Order Status data store
IF the order status is accepted by restaurant THEN
Input order details
END IF
Logic model for process 4.2
Receive the confirmed order information
Send the match request to the deliverers
Receive a confirmation of acceptance from a deliverer
Retrieve deliverer details from the Deliverer Details data store
Logic model for process 4.3
IF the order has been matched a delivery successfully THEN
Send the order information to the deliverer
END IF
Receive the confirmation of beginning to pick up the order from deliverer
Display the deliverying status of the order
Update the Order status data store
Logic model for process 4.4
IF the order has been picked up successfully THEN
Generate a track number for the order
END IF
Send the track number to the customer
Send the track number to the restaurant
Update the Oder Details data store with adding track number
Display the order status is deliverying
Update the Order Status data store
Logic model for process 4.5
Business Analysis of the Ele.me System
Page 22 of 38
Level 1 DFD & Logic Models for Process 5
Logic model for process 5.1
Retrieve Order status form Order status data store
IF order status is finished delivery THEN
Collect the finished order details
END IF
Logic model for process 5.2
Retrieve payment information form Order details data store
Compute the final payment information according to the raw payment information
Display the final payment information
Logic model for process 5.3
Receive the final payment information
Send the final payment information to the Bank
Receive the payment status notification from Bank
Files the Payment Status data store
Logic model for process 5.4
Retrieve Payment Status form Payment Status data store
Send the Payment status notification to Customer
Send the Payment status notification to Restaurant
Send the Payment status notification to Delivery
Logic model for process 5.5
Receive the payment report form Bank
File the payment report into Payment Report data store
Business Analysis of the Ele.me System
Page 23 of 38
4.2 Entity Relationship (ER) Diagram
i. Narrative for Entity Relationship Model
In this ER model as shown in the part (ii), the user of the Ele.me food delivery system has three types which are
customer, deliverer, and restaurant. Every user has a unique user ID, and they are asked to offer an available
payment method. On the system, every user can create accounts, and each account includes a unique account
ID, password, profile image, and the role which identify the purpose of the account. For instance, a restaurant
account only be used for receiving the order or uploading their menu etc. It cannot be used for placing an order.
To control the food safety issue, some of the user (restaurants and deliverers) need to submit application for
registration. All applications have a unique application ID, the date of submit, and the attachments. In detail, the
deliverer application contains deliverer’s resume and the health certificate. This type of applicat ion will be
evaluated and approved by Ele.me platform company only. While the restaurant application should be evaluated
by the third-party organization first to check the validity of the qualifications involved in the application and
approved by the Ele.me company. All approved applications will obtain the approve number.
The order is placed by the customer. Each order has a unique order ID, status, the date of generate, notes
attached, asked delivery time, pick-up information, and arrive information. The order has the food items selected
on the system. Each food item is identified by name, amount, and notes. The food items will be made by the
restaurant and be delivered by the deliverer. In order to ensuring the success of the shipping of the order, the
customer and the restaurant should provide the name, address, and contact number; and the deliverer should
provide the name and contact number. What’s more, in the delivery process, every order will be assigned with a
unique track number.
Finally, each order has a payment which has the payment ID, date of generate, the bank which implement the
pay run, the amount of payment need to give to relevant user, corresponding order ID, and the person who
conduct the real payment.
Business Analysis of the Ele.me System
Page 24 of 38
ii. ER diagram
Assumptions
• We assume that for each order it only have one unique customer.
• We assume that customers can make many orders, and not every customer on the system will make an
order.
• We assume that one customer could only make one order of only one selected restaurant one time. If the
customers want to order other food items form another restaurant, they need to place another order.
• We assume that one order must have at least one food item or the order cannot be generated.
• We assume that only when the delivery process begins, the track number of the order can be generated.
• We assume that the subclass of the user is overlapped, because a deliverer may also be a customer on the
Business Analysis of the Ele.me System
Page 25 of 38
system. However, if the deliverer wants to transfer its role to customer, it is necessary to login the customer
account. Using the deliverer account cannot order on the system.
• We assume that as the user of the system, they must have accounts, and can have different accounts.
• We assume that only the restaurants and the deliverers need to submit the application. And the subclass of
the application is disjoint.
• We assume that for the restaurants and the deliverer, get the approval of the application is the pre-
condition of creating the account.
• We assume that only the restaurant application needs to be evaluated by the third-party organization.
• The user ID, application ID, payment ID, account ID, order ID are created automatically by the system.
• We assume that the user ID is as same as the account ID.
• In order to identifying the organization on the system better, we assume that the organizations, that
participate in the evaluation stage, will be assigned with a unique organization ID number.
• We assume the address of customer is a repeating group, while the address of restaurant should only have
one constant value.
Business Analysis of the Ele.me System
Page 26 of 38
4.3 ER diagram dictionary
Business Analysis of the Ele.me System
Page 27 of 38
Business Analysis of the Ele.me System
Page 28 of 38
Business Analysis of the Ele.me System
Page 29 of 38
Section 5 – Modern Analysis (UML Models)
5.1 Use case diagram
Business Analysis of the Ele.me System
Page 30 of 38
5.2 Descriptions for each use case
Use case name: Evaluate qualification
Actor(s): Restaurant, Deliverer, Administration for market regulation, Ele.me
Description: This use case allows restaurant and deliverer to submit the applications for
registration. Their qualifications will be evaluated by Administration for market regulation
and Ele.me.
Steps: Information required [produced]:
Applicant submits the application [Application No]
If applicant is a restaurant, send the
application to the Administration for market
regulation for reviewing. And it will give the
advice report
[Advice Report No]
Ele.me will give restaurant the approval
opinion of the application through reviewing
the application and the advice report.
Application No and Advice Report No
[Approval opinion]
If applicant is a deliverer, send the application
to the Ele.me for reviewing.
Ele.me will give deliverer the approval
opinion of the application through reviewing
the application.
Application No
[Approval opinion]
Use case name: Create account
Actor(s): Customer, Restaurant, Deliverer
Description: This use case allows the customer, restaurant, and the deliverer to create
account for different purpose.
Steps: Information required [produced]:
If the user plays the role of customer and
want to create account
Customer detail (name, address, contact
number, payment method)
Create customer account for the user [Account ID]
If the user plays the role of deliverer and
requests to create account
Deliverer details (name, contact number,
payment method), Approval opinion
If the approval opinion is disapproving state,
reject request and quit.
Create deliverer account for the user [Account ID]
If the user plays the role of restaurant and
requests to create account
Restaurant details (name, address,
contact number, payment method),
Approval opinion
If the approval opinion is disapproving state,
reject request and quit.
Create restaurant account for the user [Account ID]
Business Analysis of the Ele.me System
Page 31 of 38
Use case name: Generate and process the order
Actor(s): Customer, Restaurant
Description: This use case allows customers to place orders on the system and allows
restaurants process the orders.
Steps: Information required [produced]:
The Customer select and fill the order details Order details (food item type, amount,
notes, delivery time, shipping address,
contact number)
Generate the order and send the order
details to the restaurant
[Order No]
If restaurant reject to accept the order, then
cancel the order, and quit.
If restaurant accept the order, then generate
the receipt, and send to customer
[Receipt]
Initiate “Execute delivery process” use case
Use case name: Execute delivery process
Actor(s): Customer, Restaurant, Deliverer
Description: This use case allows deliverer to ship the order. By picking up food items
from restaurant and delivering them to customer.
Steps: Information required [produced]:
Restaurant send the match deliverer request
for the order.
Order No
Generate delivery request and send to
possible deliverers.
Order details
If no deliverer accepts the delivery request,
then cancel the order and quit.
If the deliverer accepts the deliverer request,
then add deliverer details to the order and
generate the track number which will send to
the customer and restaurant.
Deliverer details
[Track No]
If the deliverer delivered the order and update
the order status of the order detail, then
initiate “Execute payment process” use case
Business Analysis of the Ele.me System
Page 32 of 38
Use case name: Execute payment process
Actor(s): Bank, Customer, Restaurant, Deliverer, Ele.me company
Description: This use case allows the customer to pay the order; allows the restaurant,
the deliverer, and the company to get paid; allows the Bank to help the system finish the
payment in the reality.
Steps: Information required [produced]:
Bank will receive the payment request for the
order
Order details, Customer details
(payment method), Deliverer details
(payment method), Restaurant details
(payment method)
Bank implement the actual payment and
upload the Payment report
Payment Report
Generate the Payment No and Payment
status for the order
[Payment No] [Payment Status]
Send the Payment No and Status to
customer
Payment No, Payment Status, Account
ID
Send the Payment No and Status to deliverer Payment No, Payment Status, Account
ID
Send the Payment No and Status to
restaurant
Payment No, Payment Status, Account
ID
Business Analysis of the Ele.me System
Page 33 of 38
5.3 Class diagram
Business Analysis of the Ele.me System
Page 34 of 38
5.4 Sequence and/or Activity Diagram
Use Case 1: Evaluate qualification
Use Case 2: Create Account
Business Analysis of the Ele.me System
Page 35 of 38
Use Case 3: Generate and process order
Use Case 4: Execute delivery process
Use Case 5: Execute payment process
Business Analysis of the Ele.me System
Page 36 of 38
5.5 State machine
Business Analysis of the Ele.me System
Page 37 of 38
Section 6 – Conclusion & Reflection
This report conducts a comprehensive analysis of the Ele.me food delivery system which is the most popular
system used in China. In order to get deeper understanding of this system, the report conduct a requirements
analysis to identifies the functions that a food delivery system should achieve in response to these requirements.
Furthermore, DFD, Logical models, EER diagrams, and UML are used for analysing how can the Ele.me system
realizes five major functions which are evaluating qualifications, creating account, generating, and processing
order, executing delivery process, and executing payment process.
Through finishing this assignment, first, I have a better understanding of this food delivery system through
research how the system interacts with external environment, as well as how the things within the system
interact with each other and work together. In addition, when using different system analysis tools, I find that
each one gives a different perspective to explain the system, and they have similarities and differences. More
importantly, I found that each stage was linked and show the recursive relationship. For example, when
analysing the system through UML, I kept going back to add and modify the previous diagrams as I progressed.
This shows that the system design is not accomplished in one time, the design results will be constantly
improved during the design process.
Business Analysis of the Ele.me System
Page 38 of 38
Section 7 – References
Shah, N., Shah, H., Sheth, S., Chauhan, R. and Desai, C., 2021. Local Food Delivery System. SSRN Electronic
Journal.
Technology and Operations Management. 2021. Ele.me, Digitizing the food delivery service in China - Technology
and Operations Management. [online] Available at:
