Use Case Diagram - E-Commerce System

Diagram9 nodesEngineering · Store RequirementsMade from one prompt
Read-only preview

The prompt

Create a use case diagram for an e-commerce system showing customer and admin actors with browse, purchase, and manage inventory use cases

Make your own version

About the framework

Define the shopping and administration scope

Customer connects to Browse Products, Search Products, Add to Cart, Checkout, and Track Order. Admin connects to Manage Inventory, Process Refund, and Checkout. The seven function boxes outline a small store rather than a full marketplace.

The Admin-to-Checkout connection is worth reviewing: your store may allow staff-assisted purchases, or you may want checkout restricted to the customer role. The sample shows participation without explaining that business rule. It also has no payment-gateway actor, shipping-service actor, system boundary, or include and extend relationships.

Adapt the functions around the store you are building. For a marketplace, add seller responsibilities; for digital goods, replace shipment tracking with access or delivery. Keep detailed screen sequences in a checkout flow so this view remains focused on who uses each function.

What's included

What you get

  • Customer and Admin actors around seven store functions
  • Customer path coverage from browsing to order tracking
  • Admin functions for inventory and refunds
  • Checkout connected to both Customer and Admin
Diagram

Use Case Diagram - E-Commerce System

use caseumlecommerce

✦ Free preview · Sign in to use

Frequently asked questions

Common questions

Why does Admin connect to Checkout?

That connection is part of the supplied example, but its purpose is unspecified. Keep it for a staff-assisted purchase scenario or remove it to match your store.

Does this show the order of checkout screens?

No. It shows actor participation in store functions. Create a user flow for address entry, payment, review, and confirmation.

How can I add returns?

Describe who requests a return and who reviews it. Ask for Request Return and Review Return functions, with the appropriate actor connections, alongside the existing Process Refund function.

Use Case Diagram - E-Commerce System

Free to start. No credit card required.

Free preview · Sign in to use