The DFD Diagram for Inventory Management System is a data flow diagram of graphical representation and commonly used also for the visualization of structured design data processing through an information system, it’s an important technique for modeling process aspects with a system’s high-level detail by showing what kinds of data will be/how to input and output from the system, where the data will come from and go to by sequentially, and where the data result will be stored through functional transformations. But It doesn’t show the timing information or the information of whether processes can be operated in sequence or in parallel (show on flowchart). Often they are a preliminary step used to create an overview of the system which can later be elaborated.
Why DFD are useful?
A data flow diagrams is one of the three essential perspectives of Structured Systems Analysis and Design Method (SSADM). It is common practice to draw the DFD Diagram for Inventory Management by Designer typically drawing interaction between the system and the outside entities which act as data sources and data sinks. In this method, both the project sponsors and the end users need to collaborate closely throughout the whole stages of the evolution of the system.
Then this context level DFD will then be exploded in order to further show the details of system being modeled. Data flow diagrams are the method of choice over technical descriptions for three principle reasons.
1. Are easier to understand by technical and non-technical audiences
2. Can provide a high level system overview, complete with boundaries and connections to other systems
3. Can provide a detailed representation of system components.
A data flow diagram represents the following:
3.1 External devices sending and receiving data
3.2 Processes that change that data
3.3 Data flows themselves
3.4 Data storage locations
Diagram for Inventory Management System reveal relationships among the business processes within an organization to external systems, external organizations, customers, other business processes and between the various components in a program. consists of four major components: External Entities/Terminators, processes, data stores and data flows.
- External Entities / Terminators - These refer or points to the outside parts of the system being developed or modeled. Terminators, depending on whether data flows into or from the system, are often called sinks or sources. They represent the information as wherever it comes from or where it goes.
- Processes – The Processes component modifies the inputs and corresponding outputs.
- Data Stores – refers to any place or area or storage where data will be placed whether temporarily or permanently.
- Data Flows – refers to the way data will be transferred from one terminator to another, or through processes and data stores.
Data flow diagrams have replaced flowcharts and pseudo code as the tool of choice for showing program design. A DFD illustrates those functions that must be performed in a program as well as the data that the function will need. In spite of its strength, the beauty of Data flow diagram lies on its dependence upon just four symbols to express program design. As a general rules, every page in a DFD should not contain more than 10 components. So, if there are more than 10 components in one processes, one or more components should have to be combined and then make another DFD to detail the combination in another page.