lecture04
lecture04
and Design
• Data Flow
• Depicts data that are in motion and moving as a
unit from one place to another in the system.
• Drawn as an arrow
• Select a meaningful name to represent the data
• For example a report produced by a process and
sent to an external entity
DFD COMPONENTS
Data Store
• A data store is a collection of data that is stored in
some way
Depicts data at rest
May represent data in
File folder
Computer-based file
Notebook
The name of the store as well as the number are
recorded in between lines
Dfd components
• Process
• Depicts work or action performed on data
so that they are transformed, stored or
distributed
• Number of process as well as name are
recorded
DFD COMPONENTS
• Source/Sink
• An external entity is a person, organization, organization unit,
or system that is external to the system, but interacts with it
(e.g., customer, clearinghouse, government organization,
accounting system)
• Depicts the origin and/or destination of the data
• Sometimes referred to as an external entity
• Name states what the external agent is
• Examples are clerks who enter data into the system or
customers who receive letters produced by the system.
Data flow diagramming mechanics
Context Diagram
• The first DFD in every business process model, whether a
manual system or a computerized system, is the context diagram.
• As the name suggests, the context diagram shows the entire
system in context with its environment.
• All process models have one context
• The context diagram shows the overall business process as just
one process (i.e., the system itself) and shows the data flows to
and from external entities.
• Data stores usually are not included on the context diagram
Data flow diagramming mechanics
DATA FLOW DIAGRAMMING
MECHANICS
• Completeness
• DFD must include all components
necessary for system
• Consistency
• The extent to which information
contained on one level of a set of nested
DFDs is also included on other levels
Guidelines for drawing dfd’s
• Timing
• Time is not represented well on DFDs
• Best to draw DFDs as if the system has
never started and will never stop.
• Iterative Development
• Analyst should expect to redraw diagram
several times before reaching the closest
approximation to the system being modeled
GUIDELINES FOR DRAWING
DFD
• Primitive DFDs
• Lowest logical level of decomposition
• Decision has to be made when to stop
decomposition
Validating the dfd
• Once you have created a set of DFDs, it is important to
check them for quality.
• There are two fundamentally different types of problems
that can occur in DFDs:
Syntax errors and semantics errors.
• “Syntax,” refers to the structure of the DFDs and
whether the DFDs follow the rules of the DFD language.
• Syntax errors can be thought of as grammatical errors
made by the analyst when he or she creates the DFD.
Validating the dfd