How to draw a use case diagram

Draw a use case diagram with actors, use cases and a system boundary, and get include and extend the right way around, using an online store as the example.

Written by
FlowDraw Team
Published
Reading time
7 min read
A FlowDraw board with a use case diagram of an online store: Customer and Admin actors, with Place order, Make payment and Apply coupon use cases.

A use case diagram is a one-page answer to two questions: who uses this system, and what can they do with it? To draw a use case diagram you need only a few symbols, plus a clear head about include and extend.

Quick Answer

A use case diagram shows what a system does for the people and systems around it. To draw one, draw a box for the system, put actors outside it and use cases inside it as ovals named with a verb and a noun, then connect each actor to its goals.

What is a use case diagram?

It is a UML behavior diagram drawn from the outside looking in. It leaves out screens, steps and data on purpose.

An online store use case diagram with numbered pins on an actor, a use case, the boundary, a line, and the include and extend arrows.
The online store, part by part

That makes it useful early: agreeing scope with a client, splitting a product into features, or checking that nobody has been forgotten.

It stops helping when the question becomes “how”:

  • For steps, draw a flowchart.
  • For messages between parts of the system, draw a sequence diagram.
  • For the main flow and the exceptions, write a description of each use case. The diagram does not replace it.

Use case diagram symbols

The numbers match the pins above.

#SymbolLooks likeMeans
1ActorStick figure outside the boxA role or outside system with a goal
2Use caseOval, named verb and nounA goal the system fulfills
3System boundaryBox with a nameWhat is in scope
4AssociationSolid lineThis actor takes part
5IncludeDashed arrow marked «include»The base always does this
6ExtendDashed arrow marked «extend»An optional addition to the base
-GeneralizationSolid line, hollow triangleA special kind of actor or use case

The example has no generalization.

Include or extend?

This is the part people argue about. Ask one question: can the base use case finish without it?

  • No, it always happens: include. Nobody places an order without paying, so “Place order” includes “Make payment”. The arrow points from the base to the included use case.
  • Yes, only sometimes: extend. An order works fine with no coupon, so “Apply coupon” extends “Place order”. The arrow points from the extension to the base.

The arrows look backward until you read them as sentences. If your sentence is false, your arrow is the wrong way around.

Two panels of the same three ovals. The left swaps include and extend. On the right, Place order includes Make payment and Apply coupon extends it.
Read each arrow as a sentence

Use both sparingly. Include pays off when two or more use cases share a piece of behavior. Extend pays off when an optional part has rules worth naming.

Reading the online store

  • Actors stay outside the box. “Customer” is on the left and “Admin” on the right, a common habit that keeps the main user first.
  • Each actor reaches only its own goals. “Customer” connects to “Browse products” and “Place order”. “Admin” connects to “Manage products” and “Ship order”.
  • “Make payment” and “Apply coupon” have no actor line. They happen inside “Place order”. If the payment provider mattered, you would add it as an actor joined to “Make payment”.
  • There is no “Log in”. It is a step on the way to a goal. Nobody comes to a store in order to log in.

How to draw a use case diagram

  1. Draw the boundary and find the actors

    Deciding what sits inside is half the value of the exercise. Ask who uses it, who runs it, and which other systems send or receive something. Name roles, not people.

    An empty box named Online store with the Customer and Admin actors outside it.
    The boundary and who stands outside it
  2. List each actor’s goals

    Ask what this actor comes here to do, and write a verb and a noun. A use case is complete when the actor could walk away satisfied.

  3. Connect actors to goals

    Use plain lines. No arrowheads are needed.

    Four goals inside the box in dark, with lines joining Customer to Browse products and Place order, and Admin to Manage products and Ship order.
    Each actor joined to its own goals
  4. Pull out include and extend

    Do it only where it makes the diagram clearer.

    Apply coupon and Make payment added in dark, joined to the faded Place order by extend and include arrows.
    Shared or optional parts come last
  5. Check the edges

    Every actor needs at least one use case, and every use case needs a line to an actor or another use case.

Draw a use case diagram in FlowDraw

The “Use case diagram” template and the UML library come with Pro or Team. On Free the template’s preview offers “Upgrade” in place of “Use template”.

The FlowDraw Templates page with Use case diagram as the one result, marked Pro.
Find it under Templates in the sidebar
  1. Open the template

    Search for “Use case diagram” under “Templates”, open the preview and click “Use template”. To start blank, open a “Blank board”, then the “Use case” group in the UML section of “Shape library”.

  2. Change the goals

    Select an oval and type. Do the same for each actor’s name.

  3. Add shapes

    The “Use case” group has “Actor”, “Use case” and “System boundary”. Click a cell and then the board, or drag it across.

  4. Draw the lines

    Pick “Association”, “Include” or “Extend” in the library, then draw from one shape to the other. “Include” and “Extend” already carry their labels. If an arrow lands at the wrong end, use “Swap ends” in “Line properties”.

  5. Settle the scope

    Click “Share” and invite people with “Can comment”. A comment pinned to an oval is a good place for “is this in scope?“. “Export” gives you a PNG or PDF for the spec.

The online store template open in the FlowDraw editor, with the toolbar at the bottom and Share at the top right.
The template open in the editor

Drawing one on Free

The notation does not depend on special shapes, so free tools can draw all of it:

  • System boundary: with nothing selected, press F and drag out a frame, then double-click its title to name it. Anything lying wholly inside moves with the frame.
  • Use cases: “Ellipse” from “Basic shapes”, or press O.
  • Actors: a labeled “Rectangle”, since UML also allows a rectangle marked «actor» above the name. The Pen tool can draw a figure in a few strokes.
  • Lines: press L with nothing selected, and set the end to “None”.
  • Include and extend: choose “Dashed” and the “Open arrow” end, then type «include» or «extend» in “Add a label”.

Use case diagram mistakes

The first one is the most common: steps dressed up as use cases. If the actor would not stop there and call it done, it is not a use case.

Two panels. On the left, Customer connects to Enter card number and Click submit. On the right, Customer connects to Browse products and Place order.
Same actor, steps on the left and goals on the right
  • Include and extend the wrong way around. Read the arrow aloud as a sentence.
  • Ovals in a chain. Arrows that show “first this, then that” turn it into a bad flowchart.
  • Actors inside the boundary. If it is part of the system, it is not an actor.
  • Job titles or names as actors. One person can be both a customer and an admin. The actor is the role they are playing at that moment.
  • Dozens of ovals. Split by actor or by feature area, with one diagram for each.

Have a system in mind? Start with a free account and sketch its boundary before anything else.

FAQ

Include means the base use case always performs the other one, so the arrow points from the base to the included use case. Extend means the other use case is optional and adds to the base under some condition, so the arrow points from the extension to the base.

Continue Reading

A FlowDraw board with a value stream map of a refund at Linden Home: five process boxes, triangles for queues, a timeline ladder and a lead time of 7 days, 40 min.

Guides·

How to make a value stream map

Learn how to make a value stream map: walk the process, time each step and wait, draw the ladder, mark the waste and plan a better future state.

A FlowDraw board with a state machine diagram of a document: Draft, In review, Approved, Published and Archived, joined by labeled transitions.

Guides·

How to draw a state machine diagram

Draw a state machine diagram in UML: states, transitions, guards and entry actions, with a document review example you can check against a simple table.

A FlowDraw board with a data flow diagram: Customer and Payment provider connect to Validate order, Take payment and Fulfill order, with two data stores.

Guides·

How to make a data flow diagram

How to make a data flow diagram: the four symbols, context and level 1 views, the rules that catch errors, and how to draw one in FlowDraw.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free