A physical DFD shows how the system is actually implemented, either at the moment (Current Physical DFD), or how the designer intends it to be in the future (Required Physical DFD). Thus, a Physical DFD may be used to describe the set of data items that appear on each piece of paper that move around an office, and the fact that a particular set of pieces of paper are stored together in a filing cabinet. It is quite possible that a Physical DFD will include references to data that are duplicated, or redundant, and that the data stores, if implemented as a set of database tables, would constitute an un-normalised (or de-normalised) relational database. In contrast, a Logical DFD attempts to capture the data flow aspects of a system in a form that has neither redundancy nor duplication. [source]
To sharpen more understanding of data flow diagrams go through these two articles on our blog before starting to construct Data Flow Diagrams.
- Concept of Data Flow Diagrams
- Symbols used in Data Flow Diagrams
- How do we begin to construct Data Flow Diagrams (DFDs)?
Difference between Logical DFD and Physical DFD
So far we considered data flow diagrams as logical models. They specify the logical process preformed on the data, i.e. the type of operations performed. Beside that logical DFDs doesn’t specify who does the operation, whether it is done manually or by computer and also where it is done. But physical DFD specifies these. For example, in figure 1(a), a physical DFD specifies that a checking clerk receives the items from vendors, checks them and rejects an item if it is not as per order. Accepted items are sent to a stores clerk who updates the inventory file. Figure 1(b), a logical DFD shows the type of operation preformed. Although the DFD is Physical or Logical but symbols used in the DFD are same. here are some major to find difference between Physical and Logical Data Flow Diagrams and different ways to construct Physical and Logical Data Flow Diagrams.
A physical DFD can be taken as the first stage for the development of logical DFD; it can be easily drawn while gathering the facts at the first step of SDLC. It can be verified by the user.
As an example, we can consider the development of a physical and logical DFD for the process of getting a cheque cashed in a bank.
Starting to build DFD is very simple if you start from Physical DFD and reach to Logical DFD.
A customer presents a cheque to a clerk. The clerk checks a ledger containing all account numbers and makes sure whether the account number in the cheque is valid, whether adequate balance is there in the account to pay the cheque, and whether the signature is authentic. After the positive report of the above operation, clerk gives the token to the customer. The clerk also debits customer’s account by the amount specified in the cheque. If the cash cannot be paid due to an error in the cheque, the cheque is returned. The token number is written on the top of the cheque, customer gives the cheque to the cashier, when the token number is called out by the cashier the customer goes to cashier with the token. The cashier checks token number, takes customer’s signature, pays cash, enters cash paid in a ledger called day book, and files the cheque.
To explain this operation, I have modeled two different DFDs, a physical and logical. The physical DFD for this operation is given in Figure in 2(a).
Same physical DFD is converted into logical DFD, by taking the functions performed at each step as same. In logical DFD each process has a well defined operation. Further, in this diagram we do not include details such as clerks/cashiers performing operations. Logical DFD for this operation is shown in Figure 2(b).
Some examples of Data Flow Diagrams build for different project scenario are :
- Tutorial on How to draw Data Flow Diagram – Train and Air Ticket Reservation System – Example
- Understanding Online Appointment System – Data Flow Diagram – Tutorials
- Tutorial on How to draw Data Flow Diagrams – Withdraw Mark-sheet from University – Example
- Returning a book to library – Data Flow Diagram – Example
- Issuing Item from Department Store – Data Flow Diagram – Example
- Issuing out a book from a library – Data Flow Diagram – Example