Data Flow Diagrams

Systems Analysis
Data and Process Modeling
1
Chapter 4
Data and Process Modeling
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
2
Objectives
™Describe data and process modeling
concepts and tools
™Explain how structured analysis
describes an information system
™Describe the symbols used in data
flow diagrams and explain the rules for
their use
™Explain the sequence of data flow
diagrams, from general to specific
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
3
Objectives
™Explain how to level(分層) and
balance(平衡) a set of data flow
diagrams
™Draw a complete set of data flow
diagrams for an information system
™Describe how a data dictionary is used
and what it contains
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
4
Objectives
™Use process description tools,
including structured English, decision
tables, and decision trees
™Explain the interaction among data
flow diagrams, the data dictionary, and
process description
™Describe the relationship between
logical and physical models
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
5
Introduction
™Systems analysis phase has three
stages
™Requirements determination (Chapter 3)
™Requirements analysis (Chapters 4 & 5)
™Evaluation of alternatives (Chapter 6)
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
6
Data Flow Diagrams
™Data flow diagrams (DFDs) show how
data moves through an information
system
™DFDs represent a logical model that
shows what a system does, not how it
does it
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-1
Package
7
Data Flow Diagrams
™Data flow diagram symbols
™Four basic symbols
™Process 處理工作
™Data flow 資料流
™Data store 資料儲存
™External entity 外部實體
™Two popular symbol sets
™Gane and Sarson
™Yourdon
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-2
Package
8
Data Flow Diagrams
™Process symbol
™Symbol is a rectangle with rounded corners
™Documented with process descriptions
™Receive input data and produces output
™Output has a different form, or content, or
both
™Details are shown in a process description
™In DFDs the process symbol appears as a
black box, underlying details not shown
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
9
Data Flow Diagrams
™Data flow symbol
™Symbol is a line with an arrowhead showing
direction
™A path for data to move from one part of the
system to another
™Represents one or more data items
™At least one data flow must enter and exit
each process
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-3
Package
10
Data Flow Diagrams
™Data flow symbol
™Incorrect process and data flow combinations
cause problems
™
™
™
Spontaneous generation
(miracle)
Black hole
Gray hole
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-4
Package
11
Data Flow Diagrams
™Data store symbol
™Symbol is a rectangle open on the right side
™Data store also is called a data repository
™Represents data that is retained for later
processing
™Must be connected to a process with a data
flow
™Must have at least one outgoing and incoming
data flow
Click to see Figure 4-5
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-6
Package
Package
12
Data Flow Diagrams
™ External entity symbol
™ Symbol is a square, usually shaded
™ Represents a person, organization, or
other system that provides data or
receives output from the system
™ External entities are called terminators
™ Source (supplies data to the system)
™ Sink (receives data from the system)
Click to see Figure 4-7
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-8
Package
Package
13
Data Flow Diagrams
™External entity symbol
™Symbol is a square, usually shaded
™Represents a person, organization, or other
system that provides data or receives output
from the system
™External entities are called terminators
™
™
Source (supplies data to the system)
Sink (receives data from the system
™Must follow specific rules for connecting DFD
symbols
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-9
Package
14
Data Flow Diagrams
™Context diagrams(全景圖)
™Top-level view that shows the systems’
boundaries scope
™Represent the results of fact-finding
™One process symbol, numbered 0 (zero)
is drawn in the center
™Data flows connect the process to the
entities
Click to see Figure 4-10
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Package
Click to see Figure 4-11
Package
15
Data Flow Diagrams
™ Conventions for data flow diagrams
1. Each context diagram must fit on one
page
2. Process name in the context diagram
should be the name of the information
system
3. Use unique names within each set of
symbols
4. Do not cross lines. Use abbreviated
identifications(# <9)
5. Use a unique reference number for
each process symbol
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
16
Data Flow Diagrams
™Diagram 0
™Displays more detail than the context
diagram
™Shows entities, major processes, data
flows, and data stores
TAKE A BREAK !!!
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-13
Package
17
Data Flow Diagrams
™Shows entities, major processes, data
flows, and data stores
™Other characteristics
™Can contain diverging data flows
™Exploded (partitioned or decomposed)
version of process 0
™Diagram 0 is the child of the parent context
diagram
™Also can be called an overview or level 0
diagram
™Can contain functional primitives
Click to see Figure 4-14
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-15
Package
18
Data Flow Diagrams
™Lower-level diagrams
™Usually necessary to show more detail
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-16
Package
19
Data Flow Diagrams
™Lower-level diagrams
™Usually necessary to show more detail
™Design must consider
™Leveling
™Balancing
™Data stores
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-17
Package
20
Data Flow Diagrams
™Leveling
™Process of drawing increasingly detailed
diagrams
™Also called exploding, partitioning, or
decomposing
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-18
Package
21
Data Flow Diagrams
™Balancing
™Maintains consistency among an entire set of
DFDs
™Parent’s input and output data flows are
preserved on the child
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-19
Package
22
Data Flow Diagrams
™Data stores
™Might not appear on higher-level DFDs
™Are shown on the the highest-level DFD that
has two or more processes using that data
store
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-20
Package
23
Data Flow Diagrams
™Strategies for developing DFDs
™Main objective is to ensure that your model is
accurate and easy to understand
™A diagram should have no more than nine
process symbols
Click to see Figure 4-21
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-22
Package
24
Data Dictionary
™Also called data repository
™Documents specific facts about the
system
™Data flows
™Data stores
™External entities
™Processes
™Data elements (data items, fields)
™Records (data structures)
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-24
Package
25
Data Dictionary
™Documenting the data elements
™Must document every data element
™Standard form or CASE tool can be used
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-25
Package
26
Data Dictionary
™Documenting the data elements
™Must document every data element
™Standard form or CASE tool can be used
™Various tools are available
™Visible Analyst is a popular example
™Key objective is to provide clear,
comprehensive information about the
system
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-26
Package
27
Data Dictionary
™Documenting the data flows
™Must document every data flow
™Standard form or CASE tool can be used
™All major characteristics must be
recorded and described
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-27
Package
28
Data Dictionary
™Documenting the data stores
™Must document every data store
™Standard form or CASE tool can be used
™All major characteristics must be
recorded and described
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-28
Package
29
Data Dictionary
™Documenting the processes
™Must document every process
™Standard form or CASE tool can be used
™All major characteristics must be
recorded and described
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-29
Package
30
Data Dictionary
™Documenting the external entities
™Must document every external entity
™Standard form or CASE tool can be used
™All major characteristics must be
recorded and described
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-30
Package
31
Data Dictionary
™Documenting the records
™Must document every record
™Standard form or CASE tool can be used
™All major characteristics must be
recorded and described
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-31
Package
32
Data Dictionary
™Data dictionary reports
™Data dictionary serves as a central
storehouse for documentation
™Using this data, you can produce many
valuable reports
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
33
Process Description Tools
™Modular design
™Process description documents a
functional primitive, using modular design
™Modular design uses three logical
structures
™Sequence
™Selection
™Iteration
Click to see Figure 4-32
Click to see Figure 4-33
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-34
Package
Package
Package
34
Process Description Tools
™Structured English
™Subset of standard English
™Describes process logic
™Use only standard sequence, selection, and
iteration structures
™Use indentation for readability
™Use a limited vocabulary
Click to see Figure 4-35
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-36
Package
35
Process Description Tools
™Decision tables
™Shows a logical structure that describes
process logic
™Every logical combination is shown
initially
™Results then can be combined and
simplified
™Programmers can use decision tables in
Click to see Figure 4-37
developing code
Package
Click to see Figure 4-38
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-39
Package
36
Process Description Tools
™Decision trees
™Graphical representation that shows a
decision table’s conditions, actions, and
rules
™Logic structure is shown horizontally
™Easy to construct and understand
™Decision table is better in complex
situations
Click to see Figure 4-40
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-41
Package
37
Logical Versus Physical Models
™Sequence of models
™A physical model shows how the
systems’ requirements are implemented
™Create a physical model of the current
system
™Develop a logical model of the current
system
™After the current system is understood,
create a logical model of the new system
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
38
Logical Versus Physical Models
™Four-model approach
™Four models
™Physical model of the current system
™Logical model of the current system
™Logical model of the new system
™Physical model of the new system
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
39
Logical Versus Physical Models
™Four-model approach
™Major benefit is having a better
grasp of the current system
functions before making any
modifications
™Major disadvantage is added time
and cost needed to develop a logical
and physical model of the current
system
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
40
SOFTWEAR, LIMITED
™The SWL team completed the factfinding process
™Rick and Carla are ready to prepare a
logical model of the system
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
41
SOFTWEAR, LIMITED
™Data flow diagrams
™Rick and Carla prepared a draft context
diagram
Click to see Figure 4-42
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-43
Package
42
SOFTWEAR, LIMITED
™Data flow diagrams
™Rick and Carla prepared a draft context
diagram
™Various revisions resulted in final version
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-44
Package
43
SOFTWEAR, LIMITED
™Data flow diagrams
™Rick and Carla prepared a draft context
diagram
™Various revisions resulted in final version
™Next steps
™Analysts prepared diagram 0
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-45
Package
44
SOFTWEAR, LIMITED
™Data flow diagrams
™Rick and Carla prepared a draft context
diagram
™Various revisions resulted in final version
™Next steps
™Analysts prepared diagram 0
™Rick partitioned the ESIP subsystem
™Carla developed other lower-level diagrams
™Logical model was completed
™Physical design issues were considered
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
Click to see Figure 4-46
Package
45
SOFTWEAR, LIMITED
™Data dictionary and process
descriptions
™Rick and Carla’s activities
™Documented the ESIP subsystem
™Met with Amy Calico to review the final model
Click to see Figure 4-50
Click to see Figure 4-47
Package
Package
Click to see Figure 4-51
Click to see Figure 4-48
Package
Package
Click to see Figure 4-49
Click to see Figure 4-52
Package
Package
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
46
SOFTWEAR, LIMITED
™Next steps
™Meet with SWL users to review the model
™Obtain input, make adjustments, get approval
™Complete the payroll system model
™Continue work on system requirements
document
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
47
End
Chapter 4
48
4-1
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
49
4-2
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
50
4-3
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
51
4-4
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
52
4-5
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
53
4-6
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
54
4-7
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
55
4-8
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
56
4-9
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
57
4-10
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
58
4-11
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
59
4-13
Shelly Cashman Series
SAD3eSystems
Analysis and Design Fourth Edition
60