DFD Examples and Creation Guide
Uploaded by
Herwina LonzonDFD Examples and Creation Guide
Uploaded by
Herwina LonzonCommon questions
Powered by AIIn Level-1 DFD, data stores play a crucial role in representing where information is temporarily held within the system during processes such as order recording or payroll calculations. They are symbolized using open-ended rectangles, illustrating storage for data that processes access or produce .
Both DFD examples start by listing activities to structure processes at a high level, such as customer orders and product production for the Lemonade Stand and bus repairs and labor recording for the Bus Garage. The Lemonade Stand focuses on product lifecycle and customer interactions, while the Bus Garage emphasizes repair and inventory management processes. Both incorporate external entities and data stores, but the contexts and specific terminologies differ according to business activities .
The use-case diagram in modern DFD construction helps in clearly defining system interactions and user requirements, leading to more organized and relevant identification of activities. It offers an advantage over the traditional method by providing a visual representation of functional requirements and their relationships with external entities, which proves beneficial in complex system analysis .
In a business process like a lemonade stand, activities such as customer ordering, product serving, payment collection, and production should be grouped into a 'Sales' functional area. Ordering raw materials, paying vendors, and managing inventory can be grouped under 'Procurement,' and labor management processes can form the 'Payroll' area. This logical grouping ensures clarity and efficiency in depicting the entire process through a DFD .
In a Data Flow Diagram, the naming conventions are: External Entities are labeled with nouns, Data Flows are named after the data they carry, Processes are identified with verb phrases or system/subsystem names, and Data Stores are also named using nouns .
Typical processes in the Bus Garage Repairs DFD include recording the Bus ID and reason for repair, determining parts needed, performing the repair, calculating parts extended and total costs, and recording labor hours. These processes facilitate systematic management of repair activities by organizing steps from problem identification to resource management and documentation for billing and performance reviews .
In constructing a Level 0 DFD, it's critical to identify the logical subsystems of the system being analyzed. Additionally, manageable subprocesses should be outlined to provide an overview of the system's operation without going into detailed tasks .
When constructing a Level 1 DFD for a payment process, subprocesses to include are recording the order, receiving the payment, and providing confirmation or receipts of transactions. Additional processes like verifying customer identity or payment method might be included to ensure a comprehensive view of transactional flow .
A context-level DFD serves as a high-level overview outlining external entities and the main system processes, while a Level 0 DFD dives deeper by identifying more detailed subprocesses and their interconnections. The context-level DFD emphasizes boundaries and external interactions, and the Level 0 DFD builds on this to provide a clearer picture of internal operations, both essential for comprehensive system understanding and planning .
The key steps in constructing a Data Flow Diagram (DFD) involve: 1) creating a list of activities, 2) constructing a context level DFD to identify external entities and major processes, 3) constructing a Level 0 DFD to identify manageable subprocesses, 4) constructing Level 1-n DFDs to depict actual data flows and data stores, and 5) checking the diagram against DFD rules .