how to draw a data flow diagram (dfd) - teesside university€¦ · ppt file · web view ·...

Data Flow Diagramming

Data Flow Diagram(DFD)Review

Learning Objective

This collection of slides will review the technique of drawing data flow diagrams.


What is a Data Flow Diagram?

• A data flow diagram (DFD) is a graphical tool that allows system analysts (and system users) to depict the flow of data in an information system.

• The DFD is one of the methods that system analysts use to collect information necessary to determine information system requirements.


What is a Data Flow Diagram?

• A Data Flow Diagram is intended to serve as a communication tool among – systems analysts– end users– data base designers– system programmers– other members of the project team


What does a DFD look like?


Why Draw Data Flow Diagrams?• To clearly and concisely communicate the flow of data

through a system.• Why use a DFD and not just text?

– “Since we previously had no way of showing a tangible model, we have had to build the next best thing, which is to use English narrative to describe the proposed system. Can you imagine spending five years’ salary on a custom built house on the basis of an exhaustive narrative description of how the house will be built? ... If you use English to describe a complex system... the result takes up so much space that it’s hard for the reader to grasp how the parts fit together

(Gane and Sarson, Structured System Analysis, 1974)

• DFD’s are easier to understand than text.


DFD Symbols and Definitions

Data flow

ExternalEntity

Data store

Process

• Process - performs some action on data, such as creates, modifies, stores, delete, etc. Can be manual or supported by computer.

• Data store - information that is kept and accessed. May be in paper file folder or a database.

• External entity - is the origin or destination of data. Entities are external to the system.

• Data flow - the flow of data into or out of a process, datastore or entity


Rules for Drawing DFD’s

A minimum of one data flowin and one data flow out of a process

A datastore must be connected to a process(either in, out, or both)

An external entity must be connected to a process(either in, out, or both)

A single data flow must only flow one way


DFD: Common Mistakes• Process has no data flowing

into it, but has data flowing out.

• Data store is hooked to external entity. This means external entity can read and write to your data file without auditing!!

• The data flow goes in two directions at once. Two or more arrows should be used to show the flow to and from each process.


DFD Example 1 • The Broadway Entertainment Company

– An important first step to consider is to look at the key processes under study. These can be itemized into a hierarchical series, where the highest level (level 0) describes a general department, or business unit, to the lowest level. The lowest level is a point where you cannot break a process into any more divisible components. These are referred to as functional primitives.


DFD: Adding Levels of Detail• The highest level, called the context diagram, is only an

overview. More detail is typically needed for system analysts.

• We add detail to a DFD by creating “levels”. The first level added after the context diagram is called level “0”.

• Each new level breaks apart one process and “decomposes” the single process into a new, more detailed DFD. A complete DFD can have many (up to 6 or 7) levels depending on the complexity of system.

• Breaking the DFD into levels is referred to as “Decomposition”.


DFD: Numbering Levels• In a DFD with many levels it’s easy to forget

which level you are on. That’s why each level has different numbering for the processes on the diagram. The ‘level’ corresponds to the number of decimal places required to define a process in it. Here’s how it works:

– Context Diagram Process labeled “0”– Level 0 Processes labeled 1.0, 2.0, 3.0, .– Level 1 Processes labeled 1.1, 1.2, 1.3, .– Level 2 Processes labeled 1.11, 1.12,...


Top (0) Process Level

B road w ay E n te rta in m en t S ys tem

M em b ers h ip1

R en ta l2

S a les3

In ven to ry4

E m p loyee5

In -S tore S ys tem0


Level 1: Membership

E n ro l1 .1

Issu e N ew C ard1 .2

R ein s ta te1 .3

Tran s ien t1 .4

M em b ersh ip1


Level 1: Rental(note this is the primitive level for this series of processes)

R en t2 .1

R etu rn2 .2

R ep orts2 .3

R en ta l2


Level 1: Sales

P roces s S a les3 .1

P roc ess R etu rn s3 .2

S a les3


Level 1: Inventory

O rd er4 .1

R ece ip t4 .2

R e jec t4 .3

Tran s fe r4 .4

In ven to ry4


Level 1: Employee

Tim e R ep ortin g5 .1

A d d / D e le te5 .2

E m p loyee5


Level 2: Membership

In p u t M em b er D a ta1 .1 .1

A s s ig n M em b er N u m b er1 .1 .2

U p d ate M em b er F ile1 .1 .3

E n ro l1 .1

In p u t M em b er N u m b er1 .2 .1

P rin t C ard1 .2 .2

Is s u e N e w C ard1 .2


U p d ate M em b er F ile1 .3 .2

R ein s ta te1 .3


U p d a te Tran s ien t R en ta l F ile1 .4 .2

Tran s ien t1 .4

M em b ers h ip1


Level 2: Sales


In p u t Item D ata3 .1 .2

U p d ate S a les F ile3 .1 .3

P rin t R ec e ip t3 .1 .4

P roc es s S a les3 .1

In p u t I tem D a ta3 .2 .1

U p d a te S a les F ile3 .2 .2

P rin t R ec e ip t3 .2 .3

P roc ess R etu rn s3 .2

S ales3


Level 2: Inventory

Is su e P u rch as e O rd e r4 .1 .1

4 .1 .2

O rd er4 .1

In p u t I tem D ata4 .2 .1

U p d a te In ven tory F ile4 .2 .2

U p d ate R ec eip ts F ile4 .2 .3

R ec e ip t4 .2

In p u t O rd er Item4 .3 .1

U p d a te R e jec tion R ep ort F ile4 .3 .2

R e jec t4 .3

In p u t I tem N u m b er4 .4 .1

U p d ate In ven tory F iles4 .4 .2

Tran s fer4 .4

In ven tory4


Level 2: Employee

In p u t E m p loyee N u m b er5 .1 .1

In p u t T im e S h eet D ata5 .1 .2

T im e R ep ortin g5 .1

In p u t E m p loyee D ata5 .2 .2

A ss ig n E m p loyee N u m b er5 .2 .3

U p d a te E m p loyee F ile5 .2 .4

A d d5 .2 .1

In p u t E m p loyee N u m b er5 .3 .1

U p d a te E m p loyee F ile5 .3 .2

D e le te5 .3

A d d / D e le te5 .2

E m p loyee5


DFD Levels: Context Diagram• First we can start to draw a general

overview. This general overview is called a “Context Diagram”.

• A Context Diagram shows three things:– all external entities– a single process labeled “0”that represents the

entire system (food ordering system)– the major information flows between the

external entities and the system.


DFD Levels: Context Diagram

• It would be impossible to understand all of the data flows, and to identify all of the ‘external entities’ relating to our information system in one pass, so we tend to draw DFD’s incrementally.


Building a DFD

• We tend to start at the context level, break processes down to Level 0, and then start to consider where data enters and exits our information system, where it is stored, and how a process converts it from one form to another. We are interested here in the movement of data and its conversion.


Building a DFD

• Note that a DFD is NOT time-sensitive, and that it is NOT a flowchart. It simply shows how and where data itself progresses through our system.

• There are other ways to add information to a chart, such as what departments are responsible for certain activities, or which is batch, realtime, etc.


DFD: Logical vs Physical• Note that the Context Diagram did NOT record the

movement of merchandise, but rather the information flow surrounding the underlying business processes. – A DFD that shows the movement of information is

called a “logical” DFD.– A DFD that shows the movement of physical stuff

(such as merchandise) is called a “physical” DFD. • The logical DFD is by far the most common type of

DFD and therefore we will focus on this in this class.


DFD for Broadway

• Corresponding to the Process Structure Charts previously outlined, Broadway’s DFD can be drawn as per the following charts:


Context Level(note there are no storage elements at this level)


Level 0


DFD: Some Final Notes• How many processes on a diagram?

– rule of thumb is to have 5 - 7 processes, if you need more, create a new level.

• Are there conventions for naming objects? – process names are verb phrases– all others are noun phrases

• How many levels should you go?– Only as many as you need to communicate adequately.

The key is efficient communication.


What have we learned?

• What is a DFD and Why do we use DFD’s?• What are the rules for drawing DFD?• What is a Context Diagram?• What is the difference between logical and

physical DFD?• What is a Level 0 DFD?• What is balancing and decomposition?


Epilogue

• The Broadway Entertainment Company DFD was created with the IBM Case tool – Rationale Rose

http://www-128.ibm.com/developerworks/rational/newto/

how to draw a data flow diagram (dfd) - teesside university€¦ · ppt file · web view ·...

Documents