Create a use case diagram for an e-commerce system showing customer and admin actors with browse, purchase, and manage inventory use cases
About the framework
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
Use Case Diagram - E-Commerce System
✦ Free preview · Sign in to use
Explore more
Frequently asked questions
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.
No. It shows actor participation in store functions. Create a user flow for address entry, payment, review, and confirmation.
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.
Free to start. No credit card required.