Scribd
Upload
2 views

java

The document outlines the functional requirements for a system with four user roles: Vendor, Customer, Delivery Runner, and Administrator, each with specific functionalities. It includes features such as user registration, menu display, food order placement, a credit-based payment system, a notification system, order history access, and a delivery system. The system ensures efficient management of orders, payments, and user interactions while providing necessary access and notifications to all users.

Uploaded by

budhah282
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2 views

java

The document outlines the functional requirements for a system with four user roles: Vendor, Customer, Delivery Runner, and Administrator, each with specific functionalities. It includes features such as user registration, menu display, food order placement, a credit-based payment system, a notification system, order history access, and a delivery system. The system ensures efficient management of orders, payments, and user interactions while providing necessary access and notifications to all users.

Uploaded by

budhah282
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

Functional Requirements

These requirements outline the core features the system should support:

1. Login Access:

o Four types of user roles with different functionalities:

 Vendor: Can manage menu items (create, read, update, delete), accept or cancel
orders, view order history, access revenue dashboard, etc.

 Customer: Can view menus, place orders, check order status, provide reviews,
view order history, and manage payments.

 Delivery Runner: Can accept or decline delivery tasks, update task statuses, and
view task history.

 Administrator: Can manage users (vendors, customers, runners), manage


customer credits, generate and send transaction receipts.

2. User Registration:

o Only administrators can register customers, vendors, and delivery runners.

o User details need to be stored in text files.

3. Menu:

o Display menus for multiple vendors at Tech University, allowing customers to easily
browse and place orders.

4. Food Order Placement:

o Customers can place orders for dining in, take-away, or delivery.

o Vendors must manage and accept/reject orders. If rejected, a refund is issued to the
customer.

5. Payment:

o Incorporate a credit-based payment system where customers pay for their orders through
their digital wallet.

o Admins can update customers’ credit and send digital receipts through notifications.

6. Notification System:

o All users should receive notifications about their actions (e.g., vendor accepting/declining
orders, administrator top-up notifications, etc.).
7. Order History:

o Both customers and vendors should have access to order and transaction history.

o Customers can reorder from past orders. Vendors can analyze order data and view
customer reviews.

8. Delivery System:

o If customers choose delivery, a delivery runner is assigned. Runners can accept or decline
tasks, and the system must ensure delivery is assigned to the next available runner if
declined.

o Delivery fees are credited back to the customer if the order is declined.

o Runners can track their earnings over time.

You might also like