What is a Use case diagram?
A UML use case diagram shows the functional requirements of a system from the perspective of its users (actors). Actors (stick figures) represent users or external systems. Use cases (ovals) represent system functions. The system boundary (rectangle) separates internal use cases from external actors. Include relationships show mandatory sub-functions; extend relationships show optional extensions. Use case diagrams are the starting point for requirements analysis and system scope definition.
How to create a use case diagram with AI
flow-chart.io generates use case diagrams from plain language in four steps. No notation knowledge required — describe what you need and the AI handles the symbols, layout, and relationships.
Describe what you need
Open flow-chart.io and type a plain-language description of the use case diagram you want. Name the key actors, systems, steps, or relationships. The more specific your description, the more accurate the generated diagram — but even a rough outline produces a solid first draft. You do not need to know any syntax or notation rules.
Review the generated diagram
The AI generates a fully editable diagram in seconds, using the correct notation for your domain. Review the nodes, connectors, and labels. Check that the relationships are accurate and the layout is readable. The diagram is a scene graph — every element is an independent object, not a flat image.
Edit any element directly
Click any node to rename it, change its type, or update its style. Drag nodes to reposition them. Add new nodes by describing what to add in the refinement panel. Remove elements you do not need. The AI can also refine the diagram for you: "add an error handling path," "split this step into two," "change the data store to a cloud icon."
Export in the format you need
Export the finished diagram as SVG for web and design tools, PNG at 2× or 4× resolution for presentations and documentation, PDF for print and client deliverables, JSON to version-control the editable scene graph alongside your code, or Mermaid (.mmd) to embed the diagram as text in GitHub or Notion.
What you can create
When to use use case diagrams
The following situations are the highest-value applications for use case diagrams in professional environments. Each represents a context where a well-constructed diagram reduces miscommunication, speeds decision-making, or produces a deliverable that would otherwise take hours to create manually.
- Requirements analysis — define system scope and user goals
- Sprint planning input — use cases map to user stories
- Stakeholder communication — show what the system will do
- Test case planning — each use case becomes a test scenario
- System boundary definition for architecture decisions
In each case, the diagram is not decoration — it is the primary artifact that the team or stakeholder actually uses to make a decision, approve a design, or onboard a new member.
Best practices for use case diagrams
Experienced practitioners consistently apply a small set of principles that separate diagrams people actually use from ones that get ignored after the meeting. Apply these to every use case diagram you create.
- Start with the happy path — the primary successful flow through the use case — before adding error handling, edge cases, and alternative routes. A diagram that shows the happy path clearly is immediately useful; one that tries to show every edge case first becomes unreadable.
- Name every element specifically. "Process order" is more useful than "Process" and "Validate payment with Stripe" is more useful than "Payment validation." Specific names let readers understand the diagram without needing a separate explanation.
- Use the right level of detail for your audience. A use case diagram for a business stakeholder should show roles and outcomes, not implementation details. A diagram for engineers should show system boundaries, technologies, and data flows. When in doubt, create two versions.
- Export a JSON copy of every diagram you want to maintain over time. The JSON export contains the complete typed scene graph — you can re-import it to continue editing after weeks or months. This is your version-controllable source of truth.
AI use case generation vs. manual diagramming
Both approaches produce editable diagrams, but they differ significantly in where time is spent and what expertise is required. Use this comparison to decide which approach fits your team's workflow.
| Aspect | flow-chart.io (AI) | Manual diagramming |
|---|---|---|
| Time to first draft | Under 60 seconds from a plain-language description | 20–60 minutes drawing and connecting shapes |
| Notation accuracy | Standards enforced automatically (gateway rules, C4 zoom levels, ERD cardinality) | Depends on practitioner knowledge; violations are common |
| Editability | Every element is a live object — click to edit any node or connector | All elements are already individually editable by design |
| Iteration speed | Describe the change in plain language; AI updates the diagram in seconds | Manual drag, delete, and reconnect for each change |
| Export formats | SVG, PNG 2×/4×, PDF, JSON, Mermaid — all from one click | Depends on the tool; some require additional steps per format |
| Learning curve | None — describe in English, AI handles notation | Notation-specific for each diagram type (BPMN, UML, C4) |
Related guides
These guides cover diagram types that are commonly used alongside use case diagrams, or that share similar audiences and use cases.
Frequently asked questions
- What is a UML use case diagram?
- A use case diagram shows the functional requirements of a system — what the system does from the perspective of its users. Actors (stick figures) interact with use cases (ovals) inside a system boundary rectangle. Include and extend relationships show how use cases relate to each other.
- What is the difference between include and extend in use case diagrams?
- Include (<<include>>) means the base use case always calls the included use case — it is mandatory. Extend (<<extend>>) means the extending use case optionally adds behavior to the base — it only triggers under certain conditions. Example: 'Place Order' includes 'Validate Cart' (always); 'Apply Coupon' extends 'Place Order' (only if customer has a coupon).
- How do I generate a use case diagram?
- Describe your system and actors: 'Use case diagram for a banking app. Actors: Customer, Teller, Admin. Customer use cases: Log In, View Balance, Transfer Funds, Apply for Loan. Teller use cases: Log In, Process Deposit, Process Withdrawal, View Account. Admin use cases: Manage Users, View Reports. Transfer Funds includes Verify Funds. Log In is included by all use cases.' The AI generates a UML use case diagram.