Data flow diagrams

UNIT 2

1
Data flow diagram

DFD is a hierarchical graphical model:

◦shows the different functions (or
processes) of the system and
◦data interchange among the processes.

2
DFD Concepts

◦Each function consumes some input

data and
◦produces some output data.

3
Data Flow Diagrams (DFDs)

A DFD model:
◦uses limited types of symbols.
◦simple set of rules
◦easy to understand:
◦it is a hierarchical model.

4
Data Flow Diagrams (DFDs)
Primitive Symbols Used for Constructing DFDs:

5
Yourdon's vs. Gane Sarson Notations

The notations that we would be following are closer to the Yourdon's

notations
You may sometimes find notations in books that are slightly different
◦ For example, the data store may look like a box with one end closed

6
7
External Entity Symbol
Represented by a rectangle
External entities are real
physical entities: Librarian

◦input data to the system or

◦consume data produced by the system.
◦Sometimes external entities are called
terminator, source, or sink.

8
Function Symbol
A function such as “search-book” is represented using a circle:
◦ This symbol is called a
process or bubble or transform. search-
book
◦ Bubbles are annotated with corresponding function names.
◦ Functions represent some activity:
◦ function names should be verbs.

9
Data Flow Symbol book-name

A directed arc or line.

◦represents data flow in the direction
of the arrow.
◦Data flow symbols are annotated with
names of data they carry.

10
Data Store Symbol

Represents a logical file:

◦A logical file can be: book-details

◦ a data structure/ database

◦ a physical file on disk.
◦Each data store is connected to a
process:
◦by means of a data flow symbol.

11
Data Store Symbol
Direction of data flow arrow: find-book
◦ shows whether data is being read
from or written into it.
Books
An arrow into or out of a data store:
◦ implicitly represents the entire data of the data store
◦ arrows connecting to a data store need not be annotated with any data
name.

12
Data Flow Model of a Car Assembly Unit

Engine Store Door Store

Chassis with Partly

Engine Assembled
Fit Fit Car Fit Paint and
Engine Doors Wheels Test
Assembled
Car Car

Chassis Store Wheel Store

13
Synchronous operation

If two bubbles are directly connected by a data flow arrow:

◦ they are synchronous

Read- number Validate-

numbers numbers
0.1 0.2 Valid
Data- number
items

14
Asynchronous operation
If two bubbles are connected via a data store:
◦ they are not synchronous.

Read- Validate-
numbers numbers
0.1 0.2
numbers Valid
Data- number
items

15
How is Structured Analysis Performed?

Initially represent the software at the

most abstract level:
◦called the context diagram.
◦the entire system is represented as a single
bubble,
◦this bubble is labelled according to the
main function of the system.

16
Tic-tac-toe: Context Diagram

Tic-tac-toe
display software

move
Human Player

17
18
19
20
Activity
Construct Level-0 DFD for UMS.

21
22
Context Diagram (LEVEL 0)

A context diagram shows:

◦data input to the system,
◦output data generated by the
system,
◦external entities.

23
Context Diagram

Context diagram captures:

◦various entities external to the system and
interacting with it.
◦data flow occurring between the system
and the external entities.
The context diagram is also called as the
level 0 DFD.

24
Context Diagram

Context diagram
◦establishes the context of the system,
i.e.
◦represents:
◦Data sources
◦Data sinks.

25
Level 1 DFD

Examine the SRS document:

◦Represent each high-level function as a
bubble.
◦Represent data input to every high-level
function.
◦Represent data output from every high-
level function.

26
Higher level DFDs

Each high-level function is separately decomposed into subfunctions:

◦ identify the subfunctions of the function
◦ identify the data input to each subfunction
◦ identify the data output from each subfunction

27
Decomposition

Decomposition of a bubble:
◦also called factoring or exploding.
Each bubble is decomposed to
◦ between 3 to 7 bubbles.

28
Decomposition

Too many bubbles:

◦more than 7 bubbles at any level
of a DFD make the DFD model
hard to understand.

29
Decompose how long?

Decomposition of a bubble
should be carried on until:
◦a level at which the function of the
bubble can be described using a
simple algorithm.

30
Context Diagram for Example

Tic-tac-toe
software
display 0

move
Human Player

31
Level 1 DFD
game
Display-
board
move 0.1
result

Validate- Check-
move winner
0.2 board 0.4

Play-
move
0.3

32
Let’s consider a software which
calculates ROOT MEAN SQUARE

33
Example 1: RMS Calculating Software

Consider a software called RMS calculating

software:
1. reads three integers in the range of -1000 and
+1000
2. finds out the root mean square (rms) of the
three input numbers
3. displays the result.

34
Example 1: RMS Calculating Software

The context diagram is simple to

develop:
◦The system accepts 3 integers from
the user
◦returns the result to him.

35
Example 1: RMS Calculating Software

Data- Compute-
items RMS
0

User result

Context Diagram

36
Example 1: RMS Calculating Software

From a cursory analysis of the

problem description:
◦we can see that the system needs
to perform several things.

37
Example 1: RMS Calculating Software

✓Accept input numbers from the user:

✓validate the numbers,
✓calculate the root mean square of the
input numbers
✓display the result.

38
Example 1: RMS Calculating Software

numbers
Read- Validate-
numbers numbers
0.1 0.2
Valid -
Data- numbers
items error

Compute-
Display rms
0.4 0.3

result RMS

39
Example 1: RMS Calculating Software

Calculate- Squared- Calculate-

squared-sum sum mean
0.3.1 0.3.2

Valid - Mean-
numbers square
Calculate-
root
0.3.3

RMS

40
Example: RMS Calculating Software
b c
a
Square Square Square
[Link] [Link] [Link]

bsq
asq csq
Sum
[Link]

Squared-sum

41
Example: RMS Calculating Software

Decomposition is never carried on

up to basic instruction level:
◦a bubble is not decomposed any
further:
◦if it can be represented by a simple set of
instructions.

42
Data Dictionary

A DFD is always accompanied by a data dictionary.

A data dictionary lists all data items appearing in a
DFD:
◦ definition of all composite data items in terms of their
component data items.
◦ all data names along with the purpose of data items.
For example, a data dictionary entry may be:
◦ grossPay = regularPay+overtimePay

43
Importance of Data Dictionary

Provides all engineers in a project with standard terminology for all

data:
◦ A consistent vocabulary for data is very important
◦ different engineers tend to use different terms to refer to the same data,
◦ causes unnecessary confusion.

44
Importance of Data Dictionary

Data dictionary provides the definition of different data:

◦ in terms of their component elements.
For large systems,
◦ the data dictionary grows rapidly in size and complexity.
◦ Typical projects can have thousands of data dictionary entries.
◦ It is extremely difficult to maintain such a dictionary manually.

45
Data Dictionary

CASE (Computer Aided Software

Engineering) tools come handy:
◦CASE tools capture the data items
appearing in a DFD automatically to
generate the data dictionary.

46
Data Dictionary
CASE tools support queries:
◦ about definition and usage of data items.
For example, queries may be made to find:
◦ which data item affects which processes,
◦ a process affects which data items,
◦ the definition and usage of specific data items, etc.
Query handling is facilitated:
◦ if data dictionary is stored in a relational database
management system (RDBMS).

47
Example of data dictionary

48
Data dictionary for RMS Software
numbers=valid-numbers=a+b+c
a:integer * input number *
b:integer * input number *
c:integer * input number *
asq:integer
bsq:integer
csq:integer
squared-sum: integer
Result=[RMS,error]
RMS: integer * root mean square value*
error:string * error message*

49
Balancing a DFD
Data flowing into or out of a bubble:
◦ must match the data flows at the next level of DFD.
◦ This is known as balancing a DFD
In the level 1 of the DFD,
◦ data item c flows into the bubble P3 and the data item d
and e flow out.
In the next level, bubble P3 is decomposed.
◦ The decomposition is balanced as data item c flows into
the level 2 diagram and d and e flow out.

50
Numbering of Bubbles:
Number the bubbles in a DFD:
◦ numbers help in uniquely identifying any bubble from its
bubble number.
The bubble at context level:
◦ assigned number 0.
Bubbles at level 1:
◦ numbered 0.1, 0.2, 0.3, etc
When a bubble numbered x is decomposed,
◦ its children bubble are numbered x.1, x.2, x.3, etc.

51
Example 2: Tic-Tac-Toe Computer Game
A human player and the computer make alternate
moves on a 3 3 square.
A move consists of marking a previously unmarked
square.
The user inputs a number between 1 and 9 to mark
a square
Whoever is first to place three consecutive marks
along a straight line (i.e., along a row, column, or
diagonal) on the square wins.

52
Example: Tic-Tac-Toe Computer Game
As soon as either of the human player or the
computer wins,
◦ a message announcing the winner should be displayed.
If neither player manages to get three consecutive
marks along a straight line,
◦ and all the squares on the board are filled up,
◦ then the game is drawn.
The computer always tries to win a game.

53
Data dictionary
Display=game + result
move = integer
board = {integer}9
game = {integer}9
result=string

54
Summary
We discussed a sample function-oriented software design methodology:
◦ Structured Analysis/Structured Design(SA/SD)
◦ incorporates features from some important design methodologies.
SA/SD consists of two parts:
◦ structured analysis
◦ structured design.

55
Summary
The goal of structured analysis:
◦ functional decomposition of the system.
Results of structured analysis:
◦ represented using Data Flow Diagrams (DFDs).
We examined why any hierarchical model is easy to understand.
◦ Number 7 is called the magic number.

56