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.

Written by
FlowDraw Team
Published
Reading time
7 min read
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.

A flowchart tells you what happens next. A data flow diagram tells you where the information goes: who supplies it, what changes it and where it is kept. Here is how to make a data flow diagram, worked through on a small order system.

Quick Answer

A data flow diagram (DFD) shows how data moves through a system, using four symbols: external entities, processes, data stores and labeled flows. It leaves out timing and decisions. To make one, draw the whole system as a single process, then split that process into numbered parts.

What is a data flow diagram?

A DFD maps information rather than work. It comes from the structured analysis methods of the 1970s, and it still answers questions such as “which parts of this system touch customer records?”

A data flow diagram for an order system with numbered pins on Customer, the Validate order circle, the Customers store and the Charge request arrow.
The four parts of a data flow diagram
  1. External entity: a person or system outside your scope. Label it with a noun, such as Customer.
  2. Process: something that changes data. Use a verb and a noun, such as Validate order.
  3. Data store: data kept for later. Use a plural noun, such as D1 Customers.
  4. Data flow: data on the move. Use a noun, such as Charge request.

It helps when you design an integration, hand a system over, or prepare a privacy or security review.

Two notations are common, and they differ mainly in processes and stores:

PartYourdon and DeMarcoGane and Sarson
External entityRectangleSquare
ProcessCircleRounded rectangle
Data storeTwo parallel linesOpen-ended box with an ID
Data flowArrowArrow

The example takes circles from the first and numbered stores from the second. If your team has a house style, keep to it.

Context diagram, level 1 and level 2

A DFD is drawn in levels, and each level opens up a process from the one above.

  • Context diagram, or level 0. The whole system is one circle named Order processing, with Customer and Payment provider around it and no stores.
  • Level 1. That circle opened into its main processes, and stores appear for the first time. The example here is level 1.
  • Level 2. One process opened again, so 2.0 becomes 2.1, 2.2 and so on. Stop when a process does one thing you can describe in a sentence.

Some textbooks call the first split “level 0”. What matters is balancing: the data entering and leaving a process must match its child diagram.

The level 1 diagram with only the outside parties and their four flows dark: Order details, Charge request, Payment result and Shipping notice.
Four flows cross the edge, and every level must keep them

Reading the order processing example

Follow one order through the three processes:

ProcessTakes inSends out
1.0 Validate orderOrder details, Customer record from D1Valid order
2.0 Take paymentValid order, Payment resultCharge request, Paid order
3.0 Fulfill orderPaid orderOrder record to D2, Shipping notice

Four choices worth copying:

  • Every arrow touches a process. Customer never writes to D1 directly, because data only changes inside a process.
  • Labels name data, not actions. A label should say what moves, not what someone does.
  • Request and result get separate arrows. They are different data, and one two-headed line would hide that.
  • There is no decision diamond. The sample leaves out rejected orders. A real model would add a flow such as Rejection notice.
Two panels of Take payment and Payment provider. The left arrows say Charge the card and If it worked. The right arrows say Charge request and Payment result.
The same arrows, labeled two ways

When to use a data flow diagram

Reach for one when the question is what data a system takes in, changes, keeps and sends out. Other questions suit other diagrams:

Your questionBetter fit
What happens first, and what depends on a yes or no?A flowchart
How are the stored tables structured?An ER diagram
In what order do systems call each other?A sequence diagram
Where does all of this run?A cloud architecture diagram

How to make a data flow diagram

  1. Set the boundary. Write one sentence saying what is inside the system. Everything else is an external entity or out of scope.
  2. List the data. Note what comes in and goes out: forms, records, messages, files, in the names people already use.
  3. Draw the context diagram. One process, the external entities and a labeled arrow for each item on your list.
  4. Split the process. Three to seven parts per diagram is a good range. Number each one and name it with a verb and a noun.
The diagram with the three numbered processes and the two flows between them dark, and the outside parties faded.
One process becomes three numbered parts
  1. Add stores. Put one wherever data waits between processes or has to outlive a single run.
The diagram with D1 Customers and D2 Orders and their two flows dark, and everything drawn earlier faded.
Stores come in only now, at level 1
  1. Check the balance. Every flow on the context diagram must appear at level 1.
  2. Walk it through. Ask someone who knows the system to trace one real record from start to end.

How to make one in FlowDraw

The “Data flow diagram” template and the “Data flow” library need Pro or Team. The pricing page lists what each plan includes.

The FlowDraw Templates page with Data flow diagram as the one result, marked Pro.
The template, with its Pro mark, on the Templates page
  1. Open the template

    In the sidebar choose “Templates”, search for “Data flow diagram”, open the preview and choose “Use template”.

  2. Replace the names

    Double-click any label to edit it. Each process number and name is its own text box on the circle, so Shift-click all three and press ⌘G (Ctrl+G on Windows) before you move them.

  3. Add processes and stores

    Open “Shape library” in the top bar, find “Data flow”, then drag “Process”, “External entity” or “Data store” onto the board.

  4. Connect and label

    Hover a shape and drag from the spot beside it to another shape, or press L with nothing selected. Select the line to open “Line properties” and type the data’s name in “Add a label”.

  5. Give each level a frame

    Press F and draw a frame around each level. Frames are the slides of “Present” and the pages of “Export”.

The data flow diagram template open in the FlowDraw editor, with Shape library and Export at the top left and Share at the top right.
The template open in the editor

To start from nothing, choose “Blank board” on Home and drag shapes in from the same library.

On Free you can use “Circle” and “Rectangle” from “Basic shapes”, and “Database” from “Flowchart” for a store. They are not strict DFD symbols, but a labeled diagram reads the same and fits inside Free’s 150 elements per board.

Common data flow diagram mistakes

  • Black holes and miracles. A process with inputs but no output swallows data. One with outputs but no input makes data from nothing. Either way, a flow is missing.
Two panels of Take payment and Fulfill order. On the left the Orders store is unconnected. On the right an Order record flow joins Fulfill order to Orders.
A missing flow, and the flow that fixes it
  • Arrows that skip a process. Entity to store, store to store and entity to entity are all wrong. Add the process that does the work.
  • Control flow on the arrows. Words like “if valid” or “then” mean you have drifted into a flowchart. Keep only the data here.
  • Unlabeled arrows. If you cannot name what moves along a line, you do not yet know what moves.
  • Levels that drift apart. A new flow added at level 2 has to appear on its parent too, or the two diagrams stop agreeing.

FAQ

External entities send or receive data. Processes change it. Data stores keep it for later. Data flows are the labeled arrows between them.

Continue Reading

A FlowDraw board with a kanban board named Launch campaign: To do, Doing and Done columns, with cards such as Pricing page copy and Q4 launch brief.

Guides·

How to make a kanban board

Make a kanban board that keeps work moving: choose columns, write clear cards, set a WIP limit and build one in FlowDraw with tags and due dates.

A FlowDraw board with a decision tree for Build or buy?: branches to On time, Late by a quarter, Fits our needs and Needs custom work, with sample payoffs.

Guides·

How to make a decision tree

Learn how to make a decision tree: the three node types, how to work out expected value, and how to draw one from a free template in FlowDraw.

A FlowDraw board with a fishbone diagram for Orders ship late: People, Process, Tools, Materials, Environment and Measurement bones with causes on each.

Guides·

How to make a fishbone diagram

A fishbone diagram sorts the possible causes of one problem. Learn to pick categories, ask why, test what you find and 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