Project Progress - Detailed design

Group Name: FIVE

FILZA SYAFIRA BINTI ZULKIFLI 202177 202177@student.upm.edu.my
NOORAMIRAH AMNANI BINTI NASRI 202369 202369@student.upm.edu.my

SHAIKH MUHAMMAD MUSTAFA BIN SHAIKH SABRI 202181 202181@student.upm.edu.my

YU ZEXU 201460 201460@student.upm.edu.my

ABDIAZIZ KAYD ISMAIL 201556 201556@student.upm.edu.my

FLOW OF EVENT

USE CASE #1 (Register)

Basic Flow

1. Customer select the “register/ signup” option.

2. The system requests that the customer to fill the registration form (ex: enter his/her
name and password)
3. After filling the form, customer have to submit the form.
4. The system validates the information in the form.
5. A new account is created for the customer.
6. The system will send verification email to confirm customer’s account.
7. Customer can log with login/password after been acknowledged by system.

Alternative Flow

1. If the customer did not fill the required information in the form, system responds with
an error message to give that information.
2. If the information provided by the customer is wrong (like confirmation password), then
also system gives the error message.

Sequence Diagram
Activity Diagram
USE CASE #2 (Order Item, Review Order, Checkout, Payment)

1. The customer chooses to create a new order.

2. The customer selects item from restaurant menu.
3. The customer can add or remove items from shopping cart.
4. The customer clicks on the cart button to review order and personal information.
5. The customer checks out the order by clicking the 'check out' button.
6. The system calculates the total amount.
7. The system displays order confirmation.
8. The system displays payment method of the order.
9. The customer can pay by their preferred method of payment.
10. The system confirms the order.

Sequence Diagram
Activity Diagram
USE CASE #3 (Track Rider)

Basic Flow:

1. The customer paid their meals.

2. The restaurant owner request to deliver the meals from the OFOS system.
3. The rider starts to deliver the meals.
4. The customer can track current location of the rider provided by OFOS and GPS system.

Altenative Flow:

1. If customer did not get their meal or the rider did not arrive at the location, customer can
cancel the order.
2. If not, the delivery will be considered complete.

Sequence Diagram
Activity Diagram
USE CASE #4 (Display and Modify Menu)

1. The restaurant owner logs in to the system.

2. The restaurant owner request to add or change the menu info in the system.
3. The restaurant owner submits the new update of menu info to the system.
4. The system will save the new menu info in the OFOS system.

Sequence Diagram
Activity Diagram
USE CASE #5 (Request Delivery)

1. The restaurant owner will request delivery to the system.

2. The system will assign the order request to a rider.
3. The rider will be notified about requested delivery before going to the restaurant.

Sequence diagram

USE CASE #6 (View customer and restaurant location)

1. The rider will go to the specific restaurant requested by restaurant owner to take the order
using GPS system.
2. The rider starts to deliver the meals.
3. The rider will go to customer’s location based on personal information filled from customer
by GPS system.
4. The rider arrives at the customer’s location.

Sequence Diagram
Activity Diagram of Use Case #5 and #6
USE CASE
CLASS DIAGRAM