UML use case diagram template
Actors, the system boundary and the use cases they take part in, with «include» and «extend» relationships.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Online banking app [system boundary]
- Sign in · Verify with 2FA · View balance + statements · Check fraud rules · Transfer money · Schedule a recurring payment · Pay a bill · Resolve a dispute
Also on the board
- Customer «actor»
- Payment network «system»
- Bank teller «actor»
- Solid line: the actor takes part «include»: always runs as part of the base case…
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Paste a table. Paste comma- or tab-separated text and it becomes a table. Tab moves to the next cell and adds rows as you go.
- Paste code as code. Paste a snippet and it becomes a code block with syntax colouring; Tab indents inside it.
- Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
Good for
- uml
- use case
- requirements
- actors
- engineer
- Designing a schema or an API before writing it
- Explaining a tricky flow in a code review or design doc
- Agreeing on team conventions such as branching and reviews
Related templates
UML class diagram
Classes with fields and methods, associations with multiplicity, and an interface with two implementations.
UML activity diagram
An order's activity flow across Customer, Store and Warehouse partitions, with a decision, a fork and a join.
ER diagram (database schema)
Entities as tables with columns, types and keys, joined by one-to-many relationships — sketch a schema before the migration.
State machine
Every state an order can be in and the events that move it — the source of truth for status logic and tests.
Non-functional requirements
Measurable quality attributes — availability, performance, security, recovery and more — with how each is verified.
PRD one-pager
A product requirements doc on one board: problem, goals, non-goals, users, requirements, metrics, risks and timeline.