- 05/13 - 05/20 (4)
- 04/22 - 04/29 (1)
- 04/15 - 04/22 (5)
- 04/01 - 04/08 (3)
- 03/25 - 04/01 (8)
- 03/18 - 03/25 (1)
- 01/08 - 01/15 (2)
12/26 - 01/02
- Data Flow Diagram - How to Evaluate DFD for Correc...
- Data Flow Diagram - Guidelines for Process Naming ...
- Rules for Drawing Logical DFD
- Data Flow Diagram - Phsical DFD to Logical DFD Con...
- Data Flow Diagram - Decomposition Process of DFD
- Data Flow Diagram - Validating DFD
- Data Flow Diagram - How to develop DFD
- Data Flow Diagram - Types of DFD
- 12/19 - 12/26 (3)
- 04/11 - 04/18 (1)
- 01/03 - 01/10 (1)
- 12/26 - 01/02 (8)
Data Flow Diagram - Phsical DFD to Logical DFD Conversion
Physical DFDs are a means to an end, not an end in themselves. They are drawn to describe an implementation of the existing system for two reasons:
· to ensure a correct understanding of the current implementation (users are generally better able to discuss the physical system as they know it through people, workstations and days of the week.)
· the implementation itself may be a problem or limiting factor; changing the implementation, rather than the system concept may provide the desired results.
A logical view steps back from the actual implementation and provides a basis for examining the combination of processes, data flows, data stores, inputs and outputs without concern for the physical devices, people or control issues that characterise the implementation.
A logical data flow diagram is derived from the physical version by doing the following:
· Show actual data needed in a process, not the documents that contain them.
· Remove routing information; that is, show the flow between procedures, not between people, offices or locations.
· Remove references to physical devices.
· Remove references to control information
· Consolidate redundant data stores.
· Remove unnecessary processes, such as those that do not change the data or data flows.