The use case diagram for online shopping system project is a way to show how shoppers and the online shopping system talk to each other. It shows how the system is put together and how it works.
Project Overview
| Name: | Online Shopping System Use Case Diagram |
| Users: | Shopping Admin, Sellers, and Buyers |
| Tools Used: | Any Diagram tools that provide use case diagram symbols. |
| Designer: | ITSourceCode.com |
Check out the articles below to find out more about diagrams and other topics.
- UML Diagrams for Online Shopping System (Complete)
- Activity Diagram for Online Shopping
- Online Shopping Cart UML Diagram
- Online Shopping System Complete UML Diagrams
- Online Shopping Project Use Case Diagram
- Use Case Diagram for E-Commerce Website
- Component Diagram for Online Shopping System
What is a Use Case Diagram
The UML use case diagram for online shopping system shows the sample behavior diagram of the software. It includes the project functions using use cases, actors, and their connections.
Importance of UML Use Case Diagram
One of the benefits of the UML use case diagram is that it assists developers and businesses with system management. It includes the procedures from the viewpoint of users.
UML Use Case Diagram for Online Shopping with Explanation
The use case diagram example for the online shopping has two main illustrations. These illustrations describe the system’s general and specific processes.
Online Shopping System General Use Case
This diagram shows the general processes of online shopping. It is based on the activities performed by the shopping admin, customers, and sellers in the system.
The diagram shows the main use cases in online shopping. Use cases include managing user information, managing and updating book information, managing borrowers, and managing transaction records.
Use Case Diagram using Include and Extend
The use case diagram using include and extend is used to elaborate on the preceding diagrams. “include” means that the use cases are needed to finish the task, while “extend” means that they are not.
Users Information Management Use Case Diagram
This diagram focuses mainly on the use case “Manage Customer’s Information”. It includes the sub-processes needed to complete user information management. This is where the admin controls the customer’s information and system access.
Manage Products Info and Status Use Case
This use case explains how the admin categorizes products and displays them on the customer’s interface. This action saves seller product info. Update product status. Numbering customer orders and deliveries.
Manage Orders and Deliveries Use Case
Orders and delivery management includes client requests and orders through deliveries. Date of reservation or order, number and price of items, total amount paid, and delivery date.
Use Case Diagram for Online Shopping System Pdf
Click the button below to download the PDF file.
How to draw a Use Case Diagram?
Time needed: 2 minutes
Here’s the complete guide on how to draw a use case diagram for an online shopping system.
- Step 1: Familiarize Use Case Diagram Symbols
For beginners, you need to familiarize first with use case symbols to be used.
- Step 2: Determine the system processes
The next step is to determine the system’s processes. They will be the use cases of your project.
You may ask the users about the typical activities done for online shopping. - Step 3: Analyze the use cases included
To determine general use cases, examine user information. Sub-cases are covered in generic use cases. Include solely internet shopping’s useful operations.
- Step 4: Plot the Use Case Diagram
Users, use cases, containers (scope), and indicators are needed to plot the diagram (association). You’ll base use cases on user feedback. First, assign users. Put a container in the diagram to segregate user and system items. Consider online shopping’s uses. Finally, map the use cases to highlight user-system interactions.
Conclusion:
The use case diagram for online shopping system pdf represents the methodology used in system development. It helps developers know the possible inputs that the project should process and perform.
Furthermore, you will discover the needed processes and connect them to the other UML diagrams. The diagram is also applicable in modeling the software’s use cases (processes). It captures the system’s flow from one process to the next.
Inquiries
If you have concerns about the Use Case Diagram for Online Shopping System, leave us your comments below.
How to read a use case diagram
A use case diagram has 3 main elements: actors (stick figures outside the system), use cases (ovals inside the system boundary), and relationships between them.
- Actor. A role played by a human or external system that interacts with the system.
- Use case. A specific goal the actor accomplishes with the system.
- System boundary. The rectangle around the use cases marks what is inside vs outside.
- Association. Line between an actor and a use case they perform.
Use case relationships
- Include. Dashed arrow with “<<include>>” — one use case ALWAYS calls another (e.g., Login is included in Place Order).
- Extend. Dashed arrow with “<<extend>>” — an optional add-on to a base use case (e.g., Apply Discount extends Place Order).
- Generalization. Solid arrow with hollow triangle — one actor or use case is a specialized form of another.
Common capstone mistakes to avoid
- Too granular. Do not create a use case for each button. Focus on business goals like “Manage Inventory.”
- Missing actors. Every use case must be associated with at least one actor.
- Confusing include vs extend. Include is mandatory; Extend is optional.
- System actors as human. External payment gateways, email servers, etc. are actors too.
- No system boundary. Missing rectangle is a common panel critique.
Where the use case diagram fits in Chapter 3
- Section 3.1 (System Overview) or 3.2 (Functional Requirements).
- List each use case with a brief description in a table alongside the diagram.
- Reference each use case when explaining the workflow in later sections.
Official documentation
Working source code for this system
Download the actual implementation of this system in your preferred language. Each project includes source code, database, and setup instructions for BSIT capstone use.
Frequently asked questions
What is a use case diagram used for in BSIT capstone?
A use case diagram shows what the system does from the user’s perspective: actors, use cases, and their relationships (include, extend, generalization). It goes in Chapter 3 and communicates the functional requirements of the system.
What tool should I use to draw the use case diagram?
Free options: draw.io, Lucidchart free tier, PlantUML, StarUML 30-day trial, Visual Paradigm Community Edition. Paid options: Microsoft Visio, Lucidchart pro, Enterprise Architect. For BSIT capstones, draw.io is the most commonly used free tool.
How detailed does the use case diagram need to be for capstone defense?
Panel members expect the diagram to match the actual system implementation. Include every major class/use case/entity relevant to the system. Omit trivial helper classes. Every diagram element should have a clear justification.
Should I use black-and-white or colored diagrams?
Black-and-white is standard for capstone documentation to match the thesis format. Use color only if it improves clarity. Ensure text is readable at printed size (10pt minimum for labels).
Where does this diagram go in the capstone documentation?
Chapter 3 (System Design and Methodology) typically holds all UML diagrams. Introduce each diagram with a 1-paragraph description explaining what it shows and how to read it.
Mary Grace G. Patulada
Programmer & Technical Writer at PIES IT Solution
Mary Grace G. Patulada (pen name ‘Nym’) is a programmer and writer at PIES IT Solution with a BSIT background from Carlos Hilado Memorial State College, Binalbagan Campus. Authored 370+ UML diagram tutorials and capstone documentation guides at itsourcecode.com. Specializes in UML (class, use case, activity, sequence, component, deployment), DFD, and ER diagrams for BSIT capstone projects.
Expertise: UML Diagrams · DFD · ER Diagrams · Use Case Diagrams · Activity Diagrams · Capstone Documentation · PHP
· View all posts by Mary Grace G. Patulada →