Scribd
Upload
81 views

Ch7 - Using Data Flow Diagrams - 2

The document discusses data flow diagrams and their levels. It explains that data flow diagrams are built in layers, with the top level being the context level. Each process may generate a lower level child diagram with the same number as the parent process. The differences between parent and child diagrams are highlighted. Typical errors in data flow diagrams and features of logical and physical data flow diagrams are also covered. Finally, the document discusses developing logical and physical data flow diagrams and introduces the concept of a CRUD matrix.

Uploaded by

Specificate tanvir
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
81 views

Ch7 - Using Data Flow Diagrams - 2

The document discusses data flow diagrams and their levels. It explains that data flow diagrams are built in layers, with the top level being the context level. Each process may generate a lower level child diagram with the same number as the parent process. The differences between parent and child diagrams are highlighted. Typical errors in data flow diagrams and features of logical and physical data flow diagrams are also covered. Finally, the document discusses developing logical and physical data flow diagrams and introduces the concept of a CRUD matrix.

Uploaded by

Specificate tanvir
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Using Data Flow Diagrams

[Chapter 7]

System Analysis and Design


-- Kendall and Kendall
-- Elias M. Awad

Prepared by - Mijanur Rahaman,


Asst. Prof. of CSE, BUBT

1/13/2019
Data Flow Diagram Levels 2

• Data flow diagrams are built in layers


• The top level is the context level
• Each process may explode to a lower level
• The lower level diagram number is the same as
the parent process number
• Processes that do not create a child diagram are
called primitive
The process on Diagram 0 that is exploded is called the parent process,
and the diagram that results is called the child diagram.

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Differences between the Parent Diagram (above) and the
3
Child Diagram (below)
(Figure 7.4)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Checking the Diagrams for Errors 4

(Figure 7.5)

Forgetting to
include a data
flow or pointing
an arrow in the
wrong direction

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Typical Errors that Can Occur in a Data Flow Diagram
5
(Payroll Example)
(Continued Figure 7.5)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Features Common of Logical and Physical Data
6
Flow Diagrams
(Figure 7.7)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
The Progression of Models from Logical to Physical 7

(Figure 7.8)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Logical Data Flow Diagram Example 8

(Figure 7.9)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Physical Data Flow Diagram Example 9

(Continued Figure 7.9)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Developing Logical Data Flow Diagrams 10

• Better communication with users


• More stable systems
• Better understanding of the business by
analysts
• Flexibility and maintenance
• Elimination of redundancy and easier
creation of the physical model

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Developing Physical Data Flow Diagrams 11

• Clarifying which processes are performed by


humans and which are automated
• Describing processes in more detail
• Sequencing processes that have to be done in a
particular order
• Identifying temporary data stores
• Specifying actual names of files and printouts
• Adding controls to ensure the processes are
done properly

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
Physical Data Flow Diagrams Contain Many Items Not
12
Found in Logical Data Flow Diagrams
(Figure 7.10)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
CRUD Matrix 13

• The acronym CRUD is often used for


– Create
– Read
– Update
– Delete
• These are the activities that must be present in a
system for each master file
• A CRUD matrix is a tool to represent where each
of these processes occurs in a system

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT
CRUD Matrix 14

(Figure 7.11)

Prepared by - Mijanur Rahaman,


1/13/2019 Asst. Prof. of CSE, BUBT

You might also like