Scribd
Upload
4 views

Group 1 – Use Case Diagram

The document outlines an Online Food Delivery System, detailing its purpose, key functionalities, and the roles of various actors including customers, restaurants, delivery personnel, and administrators. It emphasizes the importance of use case diagrams for visualizing user interactions and system requirements while also discussing their benefits and disadvantages. The conclusion highlights the diagram's role in designing a user-friendly platform that facilitates coordination among all parties involved.

Uploaded by

Christine
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views

Group 1 – Use Case Diagram

The document outlines an Online Food Delivery System, detailing its purpose, key functionalities, and the roles of various actors including customers, restaurants, delivery personnel, and administrators. It emphasizes the importance of use case diagrams for visualizing user interactions and system requirements while also discussing their benefits and disadvantages. The conclusion highlights the diagram's role in designing a user-friendly platform that facilitates coordination among all parties involved.

Uploaded by

Christine
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Online Food Delivery System – Use Case

Diagram

Group 1
Introduction

What is an Online Food Delivery System?


An Online Food Delivery System is a software application that enables users to:

• Order food online from various restaurants


• Browse restaurant menus and search for specific restaurants
• Place, cancel, and track orders
• Make online payments securely

Key Purpose:

The system streamlines the food ordering process by connecting Customers, Restaurants,
and Delivery Personnel in a seamless, efficient, and user-friendly manner.
Why Use a Use Case Diagram?
A Use Case Diagram is a visual representation of how users (called “actors”) interact within
a system to achieve specific goals (“use cases”).
They helps in:
o Identifying key interactions between users and the system
o Defining core system functionalities
o Providing a visual representation of the user journey
o Ensuring a well-structured and user-friendly application

Actors are external entities that interact with the system.


In this system there are:
o Customer – Orders food, makes payments, and tracks delivery
o Restaurant – Manages menu and processes orders
o Delivery Person – Picks up and delivers food
o Admin/System – Manages users, payments, and orders
Use Case Diagram – Online Food Delivery System
Explanation of the Use Cases
Customer:
● Login: The customer logs into their account to access the system.
● View Menu: The customer browses the restaurant's menu to see available food
items.
● Place Order: The customer selects items from the menu and creates an order.
● Make Payment: The customer pays for their order using various payment
methods.
● View Order Status: The customer tracks the progress of their order (e.g.,
pending, preparing, out for delivery, delivered).
Continuation of use cases
 Restaurant:
● Login: The restaurant staff logs into their account to manage orders.
● Manage Orders: This is a key use case encompassing several actions:
○ Viewing new orders as they come in.
○ Updating the status of orders (e.g., confirming, preparing, ready for delivery,
completed).
○ Marking orders as complete.
● View Order Status: The restaurant can view the status of orders, potentially for
customer service or internal tracking.
● Update Order Status: The restaurant updates the order status to keep the
customer informed.
● Accept/Reject Delivery Request: When a delivery request comes in, the
restaurant can accept or reject it. This might involve assigning a delivery
person.
Continuation of use cases

 Delivery Person:
● Login: The delivery person logs in to receive delivery assignments.
● Update Delivery Status: The delivery person updates the status of deliveries
(e.g., en route, arrived at restaurant, picked up order, delivered).
● Accept/Reject Delivery Request: The delivery person can accept or reject a
delivery request based on their availability and location.
Continuation of use cases
 Admin:
● Login: The administrator logs in to manage the system.
● Generate Reports: The admin generates reports on various aspects of the
system (e.g., sales, popular items, restaurant performance, delivery times).
● Manage Payments: The admin handles payment-related tasks, such as
processing refunds and payouts to restaurants.
● Manage Restaurants: The admin adds, removes, or modifies restaurant
information in the system.
● Manage Customers: The admin manages customer accounts, including
contact information and addresses.
 Manage Delivery Persons: The admin manages delivery person accounts,
including their information and availability
Benefits of using use case
diagrams
Clear communication: They provide a simple visual representation that is
easily understood by both technical and non-technical stakeholders, promoting better
communication and collaboration between different teams.
 Requirement gathering: They help identify and document key system functionalities
and user interactions, facilitating the process of gathering and analyzing requirements.
 System context understanding: By representing actors and their roles by drawings,
use case diagrams provide a clear view of the system's context and how users will
interact with it.
 Early identification of issues: Reviewing use cases early in the development cycle
can help uncover potential gaps or inconsistencies in system requirements.
 Testing foundation: Use cases can be used as a basis for creating test cases to
ensure the system meets the intended functionality.
Disadvantages of using use
case diagrams
 Complexity with detail: If too many complicated details are included in a use case diagram,
it can become cluttered and difficult to understand.
 Limited functional coverage: Use case diagrams may not capture all aspects of a system's
functionality, especially complex or technical details.
 Not for non-functional requirements: They are not well-suited for representing non-
functional requirements like performance, security, or usability.
 Time-consuming creation: Developing comprehensive use case diagrams can be time-
consuming, especially for complex systems.
 Potential for misinterpretation: Without proper documentation, the meaning of certain use
cases may be open to interpretation.
Conclusion

Key Takeaways
 A use case diagram visually represents system interactions
 It helps design a scalable, flexible, and user-friendly platform
 It ensures smooth coordination between customers, restaurants, and
delivery personnel
Group Members

1. Sibanda Babongile B N02428297Y


2. Phiri Babongile N02420196K
3. Dube Alleck N02421302W
4. Ndlovu Retsoeletsi S N02421653N
5. Tadyanehondo Tinotenda N02423671L
6. Mbonisi Fletcher Moyo N02426274L
7. Ncube Buhlebenkosi A N02428404M
8. Kaguda Christine N02421225E
9. Tlou Lorraine N02420813S
10. Nyakwima Kudakwashe N02421051P
11. Bhebhe Mnqobi N02419269X

You might also like