Scribd
Upload
267 views

Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the flow of data through an information system. It shows the sources and destinations of data, as well as where data is stored. DFDs do not show the timing or sequence of processes. There are standard notations for drawing DFDs, including symbols to represent processes, data stores, external entities, and data flows. DFDs are used in systems analysis and design to break a system down into components and identify how data moves between them.

Uploaded by

Kunal Anurag
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
267 views

Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the flow of data through an information system. It shows the sources and destinations of data, as well as where data is stored. DFDs do not show the timing or sequence of processes. There are standard notations for drawing DFDs, including symbols to represent processes, data stores, external entities, and data flows. DFDs are used in systems analysis and design to break a system down into components and identify how data moves between them.

Uploaded by

Kunal Anurag
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Data flow diagram

From Wikipedia, the free encyclopedia

Jump to: navigation, search

Data flow diagram example.[1] A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modelling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated.[2] DFDs can also be used for the visualization of data processing (structured design).

A DFD shows what kinds of data will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart).

Contents
[hide]

1 Overview 2 Advantages of DFD 3 Notations of DFDs o 3.1 Data Flow o 3.2 Processes o 3.3 Data Stores o 3.4 External Entities o 3.5 Resource store 4 Steps o 4.1 Types of DFD 4.1.1 Physical DFDs 4.1.2 Logical DFDs

4.1.3 Business System Options 4.1.4 Required DFDs 5 See also 6 Notes 7 Further reading 8 External links

[edit] Overview

Data flow diagram example.

Data flow diagram - Yourdon/DeMarco notation. It is common practice to draw the context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization. This context-level DFD is next "exploded", to produce a Level 0 DFD that shows some of the detail of the system being modeled. The Level 0 DFD shows how the system is divided into subsystems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system. Data flow diagrams were proposed by Larry Constantine, the original developer of structured design,[3] based on Martin and Estrin's "data flow graph" model of computation.

Data flow diagrams (DFDs) are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram. In the course of developing a set of levelled data flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model. There are different notations to draw data flow diagrams (Yourdon & Coad and Gane & Sarson[4]), defining different visual representations for processes, data stores, data flow, and external entities.[5]

[edit] Advantages of DFD


1. Graphic technique is superb and simple. 2. System boundaries are well described. 3. Each part of data can be represented by different level of details.[6]

[edit] Notations of DFDs


[edit] Data Flow

Data flow Notation.


Data flows from source to target except from external entity to data store and vice-versa. But data flow can be possible from process to process, external entity to process and viceversa, into and out of store from process.

Indicated by arrowhead symbol with the name of the flow above arrow.[5]

[edit] Processes

Process Notation.

Process name indicates what action to be taken on data. Indicated by circle with a process name in it. Input data flow is transformed to output data flow.[5]

[edit] Data Stores

Data Stores Notation.


It stores the information of data flow like files, database, etc. Indicated by parallel lines with a data store name above.[5]

[edit] External Entities


Represents external data processing units other than regular data flow. Depends on out of the system boundaries.[5]

[edit] Resource store

Represents physical material flow from source to target. They are usually restricted to high level diagrams.[5]

[edit] Steps
[edit] Types of DFD
Following four types are used in development project:: [edit] Physical DFDs

Project scope and current system is well-defined. Simple prototype model is drawn for estimation of purposes and to defined a basic scope. Later a more complex design can be drawn for business purpose. Uses Level 1 and leveled steps.

[edit] Logical DFDs


Drawn from current Physical DFD. Indicates the basic underlying functionality. No constraints are imposed. Uses Logical steps.

[edit] Business System Options


Use to form the base of the required business system. Uses Level 1 steps.

[edit] Required DFDs


Indicates the required system and then developed by using DFDs so as to satisfy the selected business system option. Uses Leveled steps.

[edit] See also


Control flow diagram Data island Dataflow Functional flow block diagram Function model IDEF0 Pipeline

System context diagram Structured Analysis and Design Technique Structure chart UML Activity diagram

You might also like