Data and Process Modeling
Data and Process Modeling
Process
Data Flow
Data Store
External
Entity
• Process symbol: A process receives input data and
produces output that has a different content or form
• For instance process for calculating pay uses two
inputs ( Pay rate and hours worked ) to produce one
output ( Total Pay )
• E.g. calculating sale s trends, ordering or purchasing
material ,
• Processes contain the business logic or business rules
that transform data and produces the required result
Process Name
• The process name identifies a specific
function and consists of a verb followed by a
singular noun
CACULATE COMMISION
ASSIGN FINAL GRADE
ORDER MATERIAL
VERIFY ORDER
• In DFD a process appears as black box ,where
the inputs , outputs and general function of
the process are known but the underlying
details are not shown
Data flow symbol
• Data flow is a path for data to move from on part
of the information system to the other
• Data flow represents one or more data items
• DEPOSIT, INVOICE , STUDENT GRADES, ORDER
• Data store : A data store or a repository is used to
represent a situation in which the system is
required to retain the data because one or more
processes need to use the data at some latter time
• STUDENTS , PRODUCTS, ORDERS, EMPLOYEES
• External Entity : Is a person , thing , department
outside organization or other information system that
provides data to the system or receives data from the
system
• External entities show the boundary of the of the
information system and how the IS interacts with the
outside world
• Terminators: Source(Origin ) or Sink ( destination )
• CUSTOMER, SALE REP, PAYROLL SYTEM , WAREHOUSE ,
SUPPLIER
• Miracle : A process that has No input but has
an output.
• Black hole : A process that has no out put
• GRAY hole : A process which has at least one
input and one output , but the input is
insufficient to generate an output
DATA FLOW THAT CONNECTS
DATAFLOW THAT OKAY TO USE
CONNECTS
YES NO
Process to process X
Process to entity X
Process to data X
store
Entity to entity X
Entity to data store X
Data store to data X
store
• Context diagram : Is atop level view of the IS
that shows the system boundaries and scope
• Conventions : Must fit in one page
• The process name should be the mane of the
IS
• Use unique names within the each set of
symbols
• Do not cross line
• Use a unique reference number for each
process symbol -0 for Context diagram
Exploded /Partitioned / decomposed
view of process 0
• Diagram 0 : Zooms in on the context diagrams
and shows major processes , data flows and
data stores.
• Diagram 0 also repeats the external entities
and data flows shown in the context diagram
• Each process must be serially numbered
• Diverging data flow Where the same data
flows to two more location
• Higher level : Parent
• Lower level : Child
• When you create a DFD for a system you ,
break the processing logic down into smaller
units called :
• Functional Primitives – a process that consists
of a single function and cannot be further
broke down.
• Programmers use FP’s to develop code
• Lower level diagrams : AN exploded view of
the higher level diagram
• Leveling : Is the process of drawing a series of
increasingly detailed diagrams , until the
desired degree of detail is reached .
• Balancing : maintains consistency among the
entire series of diagrams including input and
output data flows ,data definition and process
descriptions
Strategies for developing DFD
• Top down model : firs create the context diagram ,
then diagram 0, then all the child diagrams for
diagram 0 and so on .
• Bottom –UP model : First identify all the functional
primitives and , data stores , data flows and external
entities ,
• The group processes with other related symbols to
develop the lowest level diagram
• Next you group those diagrams in a logical way to
form the next higher level
• You continue your way up till you reach
diagram 0
• Use a combination of the two strategies
Data Dictionary