Session 11 final Flashcards
Iterative Process
Breaking the description of a system down into finer details
= set of charts in which one process on a given chart is explained in greater detail on another.
Balancing
Conservation of inputs & outputs to a data flow diagram process when that process is decomposed to a lower level.
What can you do to a composite data flow? (Payment & Receipt)
Split into separate data flows at the next level
(no new data can be added and all must be accounted for)
What are the guidelines for drawing DFDs (5)
Completeness
Consistency
Timing considerations
The iterative natures of drawing DFDs
Drawing primitive DFDs
What’s completeness
Extent to which all necessary components of a data flow diagram have been included and fully described
Consistency
Extent to which information contained on
one level of a set data flow diagram is also included on other levels
Timing
DFDs don’t do a very good job representing time
Iterative development
Recognizes that requirements determination & restructuring are interacting
Primitive DFD
Lowest level of decomposition
Stop Decomposition
Reduced each process to a single decision/calculation
Each data store represents data about a single entity
System user doesn’t care to see any more detail
No need to split further
Each business form/transaction is shown
Separate processes for each choice on the lowest level