Use Case Diagram Generator Use Case Diagrams
Describe your system and get a clean, labeled UML use case diagram in seconds. Stick-figure actors, oval use cases, a system boundary box, and include/extend relationships all rendered and ready to share.
Use Case Diagram Generator
Your use case diagram will appear here
Describe your system and click Generate
Use Case Diagram Examples
Browse use case diagrams made with Figviz, or generate your own above
E-Commerce / Online Shopping System
An online shopping system showing Customer and Admin actors, use cases like Browse Products, Place Order, and Manage Inventory, with include and extend relationships.
ATM Banking System
An ATM system use case diagram showing a Customer and Bank actor with use cases for withdrawals, deposits, and balance inquiries.
Library Management System
A library system use case diagram with Member and Librarian actors covering book search, borrowing, and returns.
Include and Extend Relationships
A focused example showing how <<include>> and <<extend>> relationships work between use cases in a UML diagram.
Hospital / Clinic Management System
A hospital system use case diagram covering patient registration, appointments, diagnosis, and billing across multiple actors.
Simple Use Case with Actors and System Boundary
A beginner-friendly use case diagram with two actors, a labeled system boundary rectangle, and a small set of oval use cases connected by solid lines.
What is a use case diagram generator?
A use case diagram generator is a tool that creates UML use case diagrams from a plain description of a system. Instead of placing shapes manually in a drawing app, you describe the actors (people or external systems) and the use cases (goals they want to achieve), and the tool renders a properly structured diagram with stick-figure actors, oval use cases inside a system boundary rectangle, and dashed <<include>> or <<extend>> arrows. Figviz does this with AI, so a first draft appears in seconds and you can iterate by refining the prompt.
How to make a use case diagram
Use case diagram elements: actors, use cases, system boundary, include and extend
Tips for a clear use case diagram
Keep use case names short and action-oriented: start each oval label with a verb and a noun ("Place Order", not "The customer places an order"). Limit a single diagram to one system boundary to avoid confusion. Use <<include>> sparingly for genuinely shared sub-flows (like authentication), not for every minor step. Use <<extend>> only for optional behavior that adds to a base case under a specific condition. If your diagram grows beyond about ten use cases, split it into sub-systems or create multiple focused diagrams, one per major feature area. Give Figviz a concise prompt listing actors, use cases, and any relationships you want modeled, and you will get a clean diagram on the first or second try.
Frequently asked questions
Related software diagram tools
All tools →Make your own use case diagram with Figviz
Create a free account and get starter credits to generate your own. No credit card required.