🎓 Free Capstone Projects with Full Documentation, ER Diagrams & Source Code — Updated Weekly for 2026
👨‍💻 Free Source Code & Capstone Projects for Developers

Use Case Diagram Examples — 40+ Free UML Use Cases for BSIT Capstones (2026)

itsourcecode.com hosts 40+ free Use Case diagram examples for BSIT capstone projects (2026) — complete UML use case diagrams with actors, use cases, system boundaries, and include/extend relationships for the most common capstone domains. Capstone-ready for Chapter 3 documentation. Browse by system below.

What is a Use Case Diagram?

A Use Case Diagram is a behavioral UML diagram that captures what your system DOES from the user’s perspective. It shows: Actors (stick figures — users, admins, external systems), Use Cases (ellipses — actions the system performs: Login, Add Book, Process Payment), System Boundary (rectangle around use cases — defines scope), and Relationships (association lines plus <> / <> for shared or optional behaviors). Use Case diagrams are mandatory in Chapter 3 of BSIT capstones.

How to draw a Use Case Diagram (5 steps)

  1. List the actors — every user role that interacts with the system. Common ones: Admin, User/Customer, Manager, Guest. Outside systems count too (Payment Gateway, SMS API).
  2. List the use cases — every action your system performs. Use verb-noun format: “Login,” “Manage Students,” “Generate Report,” “Process Payment.”
  3. Connect actors to use cases — draw lines from each actor to the use cases they trigger.
  4. Add includes / extends — <> for reused functionality (every transaction includes Login); <> for optional behavior (Print Receipt extends Process Payment).
  5. Draw the system boundary — rectangle around all use cases with the system name at the top. Actors stay OUTSIDE the boundary.

Featured Use Case diagrams by system domain

🎓 School, Student & Library

🏥 Hospital, Pharmacy & Healthcare

🍽️ Hotel, Restaurant & Hospitality

🛒 E-commerce, Shop & Inventory

🏦 ATM, Banking & Authentication

🚗 Transport, Travel & Reservation

📘 Tutorials & References

About this Use Case diagram collection

Curated since 2015 by PIES Information Technology Solutions, Binalbagan, Negros Occidental, Philippines. Used by 12,000+ BSIT students monthly. Pair each Use Case with the matching ER Diagram and DFD for a complete Chapter 3 documentation set.

Related UML diagram collections

Frequently Asked Questions

What is a Use Case Diagram and when do I need one?
A Use Case Diagram is a UML behavioral diagram showing actors (users), use cases (system actions), and their interactions. You need one in Chapter 3 of every BSIT capstone documentation — it defines system scope and what each user role can do. It is the cleanest way to communicate "what does this system do?" to a non-technical panel.
What is the difference between an actor and a use case?
An actor is a role outside the system that interacts with it (User, Admin, Customer, Payment Gateway, SMS Service). Drawn as a stick figure. A use case is an action the system performs in response (Login, Place Order, Generate Report). Drawn as an ellipse inside the system boundary. Actors stay OUTSIDE the system boundary rectangle.
What is include vs extend in Use Case Diagrams?
<<include>> means "use case A always requires use case B to complete" (every Place Order <<include>> Login — you must be logged in to place an order). <<extend>> means "use case A optionally adds behavior to use case B" (Print Receipt <<extend>> Place Order — receipts are optional). Use include for mandatory reuse, extend for optional behavior.
How many use cases should my Use Case Diagram have?
A typical BSIT capstone Use Case Diagram has 10-25 use cases. Fewer than 5 means your scope is too small. More than 30 makes the diagram unreadable — split into multiple diagrams by subsystem (Customer-facing, Admin-facing, Reporting). Each use case should be a verb-noun action ("Add Book," "Process Payment"), not a feature category ("User Management").
What free tool should I use to draw a Use Case Diagram?
draw.io / diagrams.net — free, web-based, has UML Use Case shapes built in. Lucidchart Free — prettier but limited free tier. Visual Paradigm Community — full UML support, desktop install. PlantUML — text-based, version-controllable. Start with draw.io for capstone — fastest learning curve.
Should I draw separate use case diagrams for each user role?
For most BSIT capstones — no. One Use Case Diagram showing all actors and use cases is enough. Only split into multiple diagrams if you have 4+ user roles and 30+ use cases. Some schools require a separate UCD per role for clarity — check your documentation template. When in doubt, ask your adviser before drawing.
How often is this Use Case Diagram collection updated?
New Use Case Diagrams are added regularly as we encounter new capstone domains. Existing diagrams are revised when UML notation standards update. Last refreshed: May 2026.

Itsourcecode.com is your trusted resource for free source code, capstone projects with full documentation, and step-by-step programming tutorials.

Built by PIES IT Solutions

Binalbagan, Negros Occidental, Philippines

Quick Links

Top Categories

Get Free Capstone Resources

Subscribe for weekly updates and free resources delivered to your inbox.

© 2026 Itsourcecode.com | All rights reserved|
Built with ❤️ by PIES Information Technology Solutions