Use Case Diagram – Amazon E-Commerce Platform
A use case diagram is a visual representation of the interactions between actors (external entities) and the system (Amazon, in this case). It shows who does what, helping students visualize functional requirements.
Actors Involved:
- Customer
- Seller
- Admin
- Payment Gateway
- Delivery Partner
- Guest User
Primary Use Cases
For Customer:
- Register and Login
- Search Products
- View Product Details
- Add to Cart / Wishlist
- Place Order
- Make Payment
- Track Order
- Cancel or Return Order
- Rate and Review Product
For Guest User:
- Browse Products
- View Offers and Categories
- Register / Login to make a purchase
For Seller:
- Register as Seller
- Add / Update Product Listings
- Manage Inventory
- View Orders
- Ship Product
- Respond to Customer Queries
For Admin:
- Approve Seller Accounts
- Block Suspicious Users
- Manage Product Categories
- Monitor System Activities
- Handle Customer Complaints
- Manage Promotions and Ads
For Payment Gateway:
- Process Payment
- Authorize Transactions
- Handle Refunds
For Delivery Partner:
- Accept Order Pickup
- Update Delivery Status
- Confirm Delivery or Return
Diagram Description:
- Actors are placed outside the system boundary (a rectangle).
- Use cases are represented as ovals inside the system.
- Lines connect actors to the use cases they are involved in.
- You may use
<<include>>
and<<extend>>
relationships where: -
-
<<include>>
: Shared logic between use cases (e.g., Payment included in Place Order). -
<<extend>>
: Optional or conditional logic (e.g., Guest user extends to Register).
-