Data Flow Diagram Symbols
Data Flow Diagram Symbols
and Tips
Reading time: about 7 min
Data flow diagrams visually represent systems and processes that would be hard
to describe in a chunk of text. You can use these diagrams to map out an existing
system and make it better or to plan out a new system for implementation.
Visualizing each element makes it easy to identify inefficiencies and produce the
best possible system.
Read our full data flow diagrams overview to learn more about best practices
when building DFDs.
Both physical and logical data flow diagrams can describe the same information
flow. In coordination they provide more detail than either diagram would
independently. As you decide which to use, keep in mind that you may need
both.
Level 0 DFDs, also known as context diagrams, are the most basic data flow
diagrams. They provide a broad view that is easily digestible but offers little
detail. Level 0 data flow diagrams show a single process node and its connections
to external entities.
Level 1 DFDs are still a general overview, but they go into more detail than a
context diagram. In a level 1 data flow diagram, the single process node from the
context diagram is broken down into subprocesses. As these processes are
added, the diagram will need additional data flows and data stores to link them
together.
Data flow diagram symbols and notation
Depending on the methodology (Gane and Sarson vs. Yourdon and Coad), DFD
symbols vary slightly. However, the basic ideas remain the same. There are four
basic elements of a data flow diagram: processes, data stores, external entities,
and data flows. The picture below shows the standard shapes for both
methodologies.
How to create a data flow diagram
Now that you have some background knowledge on data flow diagrams and how
they are categorized, you’re ready to build your own DFD. The process can be
broken down into 5 steps:
Nearly every process or system begins with input from an external entity and
ends with the output of data to another entity or database. Identifying such
inputs and outputs gives a macro view of your system—it shows the broadest
tasks the system should achieve. The rest of your DFD will be built on these
elements, so it is crucial to know them early on.
Once you’ve identified the major inputs and outputs, building a context diagram
is simple. Draw a single process node and connect it to related external entities.
This node represents the most general process information undergoes to go
from input to output.
The example below shows how information flows between various entities via an
online community. Data flows to and from the external entities, representing both
input and output. The center node, “online community,” is the general process.
The single process node of your context diagram doesn’t provide much
information—you need to break it down into subprocesses. In your level 1 data
flow diagram, you should include several process nodes, major databases, and all
external entities. Walk through the flow of information: where does the
information start and what needs to happen to it before each data store?
To enhance the detail of your data flow diagram, follow the same process as in
step 3. The processes in your level 1 DFD can be broken down into more specific
subprocesses. Once again, ensure you add any necessary data stores and flows—
at this point you should have a fairly detailed breakdown of your system. To
progress beyond a level 2 data flow diagram, simply repeat this process. Stop
once you’ve reached a satisfactory level of detail.
When your diagram is completely drawn, walk through it. Pay close attention to
the flow of information: does it make sense? Are all necessary data stores
included? By looking at your final diagram, other parties should be able to
understand the way your system functions. Before presenting your final diagram,
check with co-workers to ensure your diagram is comprehensible.
https://www.lucidchart.com/pages/data-flow-diagram
https://youtu.be/FkLLS6BuDsg