UML for Cafeteria System

System Overview

1. Features / Use Cases



• Customer is able to register a card at management office.

• Customer is able to reload card balance at management office.

• Customer is able to check card balance at checkout machine.

• Customer is able to checkout at checkout machine.

• Cashier is able to charge card and return balance.

• Administrator is able to check all transactions.

• Administrator is able to print transactions report.

2. Stakeholders



• Customer

• Cashier

• Manager

• Administrator

Use Case Diagram

Deployment Diagram

Sequence Diagram

Scenario 1: Register a card



Scenario 2: Reload balance

Scenario 3: Checkout

Scenario 4: Search transactions

Scenario 5: Print transactions summary

Component Diagram