Use-Case Name

Priority
Primary Business Actor

Other Participating Actors

Other Interested Stakeholders

Description

Precondition

Trigger

Typical Course of Events

Alternate Courses
Alternate Courses

Conclusion

Postcondition

Business Rules
Assumptions
Open Issues

Use-Case Name
Priority
Primary Business Actor
Other Participating Actors

Other Interested Stakeholders

Description

Precondition

Trigger
Typical Course of Events
Alternate Courses

Conclusion
Postcondition

Business Rules

Assumptions
Open Issues

Use-Case Name
Priority
Primary Business Actor
Other Participating Actors

Other Interested Stakeholders

Description

Precondition

Trigger
Typical Course of Events

Alternate Courses

Conclusion
Postcondition

Business Rules

Assumptions
Open Issues
Create customer account
High
Customer
Seller (Primary System Actor)
Gojek Driver (External Server Actor)
Bank (External Receiver Actor)
Marketing and Sales
This use case describes the event of Online customer creates customer account by entering basic
information and then following up with one or more adresses and a credit or debit card.
Customer account subsystem must be available
Credit/debit authorization services must be available
New Customer wants to set up account online
Actor Action
Step 1: Customer indicates desire to create
customer account and enters basic customer
information

Step 4: Customer enters one or more addresses

Step 7: Customer enters credit/debit card

information

Alt-Step 7: If enter credit/debit card information components not complete, system will give rem
complete all the components, if its is cannot be provide, terminate use case
Alt-Step 9: If system can not verify credit/debit card information, system will give reminder to re
all the components, if its is cannot be provide, terminate use case

The use case concludes when the customer account already created and saved
Customer must be created and saved
One or more addresses must b created and saved
Credit/debit card information must be validated
Account must be created and saved
Address and Account must be associated with customer
None
Customer already downloaded the application system
None

Shipping the Order Items

High
Shipping Clerk (Gojek Driver)
Seller (Primary System Actor)
Customer (Primary System Actor)
Sales, Marketing, Shipping, Gojek Company.
This use case describes the event of shipping retrieves sale details, finds each item and records i
shipped, records which items are not available, and sends shipment.

Customer and address must exist

Sale must exist
Sale items must exist
Shipping is notified of a new sale to be shipped
Actor Action
Step 1: Shipping requests sale and sale item
information
Step 3: Shipping assigns shipper

Step 5: For each available item, shipping records

item is shipped

Step 7: For each unavailable item, shipping records

back order

Alt-Step 4: If shipper is not available to that location, system will give reminder to select anothe
or waiting for awhile until the shipping clerk are available, if its is cannot be provide, terminate u

Alt-Step 6: If order item is damaged or not available, system will give reminder to get new item
updated item quantity, if its is cannot be provide, terminate use case

The use case concludes when the sale items already shipped.
Shipment is created and associated with shipper
Shipped sale items are updated as shipped and associated with the shipment
Unshipped items are marked as on back order
None
Marketplace system are integrated with Gojek Application

None

Create New Order

High
Seller
Customer (Primary System Actor)
Gojek Driver (External Server Actor)
Sales, Marketing and Shipping.
This use case describes the event when customer create a new order, add items to the cart, then
and system verify customer information, verify the item availibility, shipping an order item and fi
order.

Customer must exist

Catalog, Products and Inventory items must exist for request item
Order is notified of a new sale to be followed up
Actor Action
Step 2: Seller verifies customer information

Step 3: Seller verifies the item availibility

Step 4: Seller preparing order item
Step 5: Seller request shipping to assigns shipper.
Step 7: Seller shipping an order item
Alt-Step 2: If customer does not exist, then seller pauses this use case.
Alt-Step 3: If an order item is not in stock, the customer can choose not to purchase item (cance
order) or request item be added as a back-ordered item, if its is cannot be provide, terminate us

The use case concludes when the customer has been received the order items.
Order item must be created
Inventory items must have the quantity on hand updated
The order must be related (associated) to a customer
None
Customer has been create a new order and completed the payment

None
e customer creates customer account by entering basic
ne or more adresses and a credit or debit card.
lable
e available
line
System Action

Step 2: System creates a new customer

Step 3: System prompts for customer addresses

Step 5: System creates addresses

Step 6: System prompts for credit/debit card

Step 8: System creates account

Step 9: System verifies authorization for credit/debit

card
Step 10: System associates customer, address and
account

Step 11: System returns valid customer account details

mation components not complete, system will give reminder to

ot be provide, terminate use case
debit card information, system will give reminder to re-entering
ide, terminate use case

er account already created and saved

d saved
dated

with customer

tion system

y.
ng retrieves sale details, finds each item and records it is
able, and sends shipment.

pped
System Action
Step 2: System look up sale and returns customer,
address, sale, and sale item information.
 Step 4: System creates shipment and associates it with
the shipper.
Step 6: System updates sale item as shipped and
associates it with shipment

Step 8: System updates sale item as on back order

Step 9: System records shipment cost.

at location, system will give reminder to select another location
rk are available, if its is cannot be provide, terminate use case

t available, system will give reminder to get new item and

rovide, terminate use case

ms already shipped.
hipper
d and associated with the shipment
rder

ojek Application
 stomer create a new order, add items to the cart, then seller
erify the item availibility, shipping an order item and finalize the

st exist for request item

wed up
System Action
Step 1: System create a new order by customer
initiated

Step 6: System found a shipper.

Step 6: Finalize order
n seller pauses this use case.
the customer can choose not to purchase item (cancelation
-ordered item, if its is cannot be provide, terminate use case

er has been received the order items.

n hand updated
a customer

d completed the payment