
π Student Projects (College Reports) Β· Use Case
Customers, sellers, the admin and outside services in an online shopping website.
Drawing diagramβ¦
Use case diagram for an online shopping system: a customer browses products, adds to cart, checks out, pays, tracks orders and writes reviews; a seller lists products and manages stock; the admin manages categories and handles complaints; the payment gateway processes payments and the courier updates delivery status. Checkout includes payment; applying a coupon extends checkout.
flowchart LR
customer(["π€ Customer"])
seller(["πͺ Seller"])
admin(["π‘οΈ Administrator"])
pay(["π³ Payment Gateway"])
courier(["π Courier"])
subgraph SYS ["π Online Shopping System"]
UC1(["Browse products"])
UC2(["Add to cart"])
UC3(["Checkout"])
UC4(["Make payment"])
UC5(["Apply coupon"])
UC6(["Track order"])
UC7(["Write review"])
UC8(["List products"])
UC9(["Manage stock"])
UC10(["Manage categories"])
UC11(["Update delivery status"])
end
customer --> UC1
customer --> UC2
customer --> UC3
customer --> UC6
customer --> UC7
seller --> UC8
seller --> UC9
admin --> UC10
courier --> UC11
UC4 --> pay
UC3 -.->|"includes"| UC4
UC5 -.->|"extends"| UC3Who uses a college library system and what each of them can do: members, the librarian and the system administrator.
The database of a library system: books and their copies, authors, members, loans, reservations and fines, with keys and cardinality.
How data moves through a library system: members and the librarian, the main processes, and the data stores they read and write.
The main classes of a library system with attributes, methods and UML relationships.
The steps when a member borrows a book: checks, loan record and the copy status update.
What students, examiners and the administrator do in an online examination system.