How do I make a use case diagram?

Name your system and list its actors (the people or external systems that interact with it). For each actor, list the goals (use cases) they want to achieve inside the system boundary. Connect actors to use cases with solid lines, then add dashed > or > arrows where needed. Type all of this into Figviz and it generates the diagram for you.

Is the use case diagram generator free?

Yes. You can generate use case diagrams on the free credits every account starts with. Buying any pay-as-you-go credit pack removes the watermark and unlocks higher resolutions. Credits never expire.

What are actors and use cases?

An actor is any person, role, or external system that interacts with the system you are modeling. It is drawn as a stick figure outside the system boundary. A use case is an oval inside the system boundary that represents a goal or action the actor wants to accomplish, such as "Book Appointment" or "Process Payment".

What is the difference between include and extend relationships?

> means a use case always calls another use case as a required sub-step. For example, "Checkout" always includes "Process Payment". > means a use case can optionally add behavior to a base use case under certain conditions. For example, "Apply Discount" might extend "Checkout" only when a coupon code is entered. Include arrows point from the base to the included case; extend arrows point from the extension to the base.

Can I use these diagrams for software documentation or class assignments?

Yes. Download a high-resolution PNG (up to 4K) for embedding in design docs, requirements specs, slides, and class assignments. As an AI tool it is great for drafting and teaching; review the diagram for accuracy before including it in formal deliverables. Diagrams from a paid account can be used in your own documentation and materials.

AI-Powered

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.

✓Actors and system boundary✓Include and extend relationships✓Classic UML notation✓Slide and doc readyLast updated: 2026-06-21

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.

e-commerceUMLinclude

ATM Banking System

An ATM system use case diagram showing a Customer and Bank actor with use cases for withdrawals, deposits, and balance inquiries.

bankingATMUML

Library Management System

A library system use case diagram with Member and Librarian actors covering book search, borrowing, and returns.

libraryUMLmanagement

Include and Extend Relationships

A focused example showing how <<include>> and <<extend>> relationships work between use cases in a UML diagram.

includeextendUML

Hospital / Clinic Management System

A hospital system use case diagram covering patient registration, appointments, diagnosis, and billing across multiple actors.

hospitalclinicUML

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.

beginnerUMLactors

Prompt templates you can copy

Start with one of these examples, then adapt the subject, labels, data, or layout for your own use.

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.

Create a clear labeled UML use case diagram for an e-commerce online shopping system. Actors: Customer and Admin (stick figures outside the system boundary). Use cases inside: Browse Products, Search Products, Add to Cart, Checkout, Track Order (Customer); Manage Products, View Orders, Process Refund (Admin). Checkout <<include>> Process Payment. Place Order <<extend>> Apply Discount. Classic UML style, black on white, readable labels. White background.

ATM Banking System

An ATM system use case diagram showing a Customer and Bank actor with use cases for withdrawals, deposits, and balance inquiries.

Create a clear labeled UML use case diagram for an ATM banking system. System boundary labeled "ATM System". Actors: Customer and Bank (stick figures outside). Use cases inside: Insert Card, Authenticate PIN, Withdraw Cash, Deposit Cash, Check Balance, Transfer Funds, Print Receipt. Withdraw Cash <<include>> Authenticate PIN. Deposit Cash <<include>> Authenticate PIN. Print Receipt <<extend>> any transaction. Classic UML black-on-white style, clean labels. White background.

Library Management System

A library system use case diagram with Member and Librarian actors covering book search, borrowing, and returns.

Create a clear labeled UML use case diagram for a library management system. System boundary labeled "Library System". Actors: Member and Librarian (stick figures outside). Member use cases: Search Books, Borrow Book, Return Book, Renew Book, Pay Fine. Librarian use cases: Add New Book, Remove Book, Manage Members, Generate Reports. Borrow Book <<include>> Check Availability. Pay Fine <<extend>> Return Book. Classic UML textbook style. White background.

Include and Extend Relationships

A focused example showing how <<include>> and <<extend>> relationships work between use cases in a UML diagram.

Create a labeled UML use case diagram specifically demonstrating include and extend relationships. System boundary labeled "Order System". Actors: Customer (stick figure). Use cases: Place Order, Process Payment, Apply Coupon, Send Confirmation Email. Place Order <<include>> Process Payment (required step). Place Order <<extend>> Apply Coupon (optional). Place Order <<extend>> Send Confirmation Email (optional). Label each dashed arrow with <<include>> or <<extend>>. Add short annotations explaining what each relationship means. Classic UML style. White background.

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

Identify the system: name the system you are modeling and draw a rectangle labeled with that name to represent the system boundary.

List the actors: find everyone (or every external system) that interacts with the system. Actors go outside the system boundary as stick figures.

Identify use cases: for each actor, list the goals they want to achieve. Each goal becomes an oval inside the system boundary.

Connect actors to use cases: draw a solid line from each actor to the use cases they participate in.

Add relationships: use a dashed arrow labeled <<include>> for a use case that is always called by another, and <<extend>> for an optional extension.

Describe everything in plain English to Figviz, choose a style, and generate. Refine the prompt to add missing actors or relationships.

Use case diagram elements: actors, use cases, system boundary, include and extend

Actor: a stick figure representing a person, role, or external system that interacts with the system. Actors live outside the system boundary.

Use case: an oval labeled with a goal the actor wants to accomplish (for example "Place Order" or "Generate Report"). Use cases live inside the system boundary.

System boundary: a rectangle that separates the system being modeled from everything outside it. Label the rectangle with the system name.

<<include>>: a dashed arrow showing that one use case always calls another as a required sub-step. Arrow points from the base use case to the included one.

<<extend>>: a dashed arrow showing that one use case optionally extends another under certain conditions. Arrow points from the extension to the base use case.

Association: a solid line between an actor and a use case showing that the actor participates in that use case.

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

A use case diagram generator is a tool that builds UML use case diagrams from a description of your system. With Figviz you type the actors, use cases, and any include or extend relationships in plain English, and the AI produces a labeled diagram with stick-figure actors, oval use cases, and a system boundary rectangle in seconds.

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.