We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21
Data Flow Diagrams
What is a Data Flow Diagram?
A data flow diagram (DFD) is a
graphical representation of the movement of data between external entities, processes and data stores within a system.
Simply put, DFD’s show how data
moves through an information system. DFD Symbols Process
The work or actions performed on data so that they
are transformed, stored, or distributed.
Process labels should be verb phrases!
Data Flow
A path for data to move from one part of the system
to another. Data in motion! Arrows depict the movement of data. NO VERBS Data Store
Used in a DFD to represent data that the system
stores Data at rest! Labels should be noun phrases (NO VERBS) External Entity aka Source/Sink
The origin or destination of data!
This represents things outside of the system. Source – Entity that supplies data to the system. Sink – Entity that receives data from the system. The labels should be noun phrases! General DFD Rules YES NO A process to another process
A process to an external entity
A process to a data store
An external entity to another external entity
An external entity to a data store
A data store to another data store
Physical and logical data flow diagrams (logical) • focus on what happens in a particular information flow: what information is being transmitted, what entities are receiving that info, what general processes occur, etc.
• The processes described in a logical DFD are
business activities—a logical DFD doesn’t delve into the technical aspects of a process or system, such as how the process is constructed and implemented.
• So you don’t need to include details like
configuration or data storage technology.
• Non-technical employees should be able to
understand these diagrams, making logical DFDs an excellent tool for communicating with project stakeholders. Physical and logical data flow diagrams Physical data flow diagrams
• focus on how things happen in an
information flow.
• These diagrams specify the software,
hardware, files, and people involved in an information flow.
• A detailed physical data flow diagram can
facilitate the development of the code needed to implement a data system. Physical data flow diagrams Data flow diagram levels Level 0 DFD: • 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.
• For instance, the example shown below
illustrates the hotel reservation process with the flow of information between admin and guests. Data flow diagram levels Level 0 DFD: Data flow diagram levels Level 1 DFD:
• Level 1 DFDs are still a general overview, but they
go into more detail than a context diagram.
• In level 1 DFD, the single process node from the
context diagram is broken down into sub- processes.
• As these processes are added, the diagram will
need additional data flows and data stores to link them together.
• In the hotel reservation example, this can include
adding the room selection and inquiry processes to the reservation system, as well as data stores. Data flow diagram levels Level 1 DFD: Data flow diagram levels Level 2+ DFD:
• Level 2+ DFDs simply break processes
down into more detailed sub-processes. In theory, DFDs could go beyond level 3, but they rarely do.
• Level 3 data flow diagrams are detailed
enough that it doesn’t usually make sense to break them down further.
The level 2 diagram below expands on the
hotel reservation process to include more granular processes involved, such as the cancellation and confirmation processes and subsequent connected data flows. Data flow diagram levels Level 2+ DFD: How to create a data flow diagram
1. Identify major inputs and outputs in your
system
2. Build a context diagram
3. Expand the context diagram into a level 1
DFD
4. Expand to a level 2+ DFD
5. Confirm the accuracy of your final
diagram Advantages of DFDs Simple graphical techniques which are easy to understand Helps define the boundaries of the system Useful for communicating current system knowledge to users Explains the logic behind the data flow within the system Used as the part of system documentation file Rottman makes you do these in design! Group Exercise
Get into your project groups and figure out
the best solution for the level 0 DFD for the National Merchandising Case! When you are done have one team member come and put your solution on the board.