Data Flow Diagram With Examples & Tips

Data Flow Diagram with Examples & Tips
http://projectcommunityonline.com/data-flow-diagram-with-examples-ti...
Home About Store Articles Community Hub Free Stuff Whats On Contact Us Members Area
+
Install Adobe PDF Reader

May 8, 2012 By Modern Analyst presented by Project Community
Feature
This article describes the Data Flow Diagram devised by Larry Constantine in the 1970s as part of the Structured Analysis movement. It follows logically from the Context Diagram article in which we used a much simplified Data Flow Diagram to show a proposed system in the context of its external interfaces and actors. Introduction The Data Flow Diagram (DFD) provides a graphical representation of the flow of data through a system. It shows logically what information is exchanged by our system processes and external interfaces or data stores, but it does not explicitly show when or in what sequence the information is exchanged. Data Flow Diagrams are one of the three essential perspectives of the Structured Systems Analysis and Design Method (SSADM) that predates the more recent object oriented design methods and notations such as UML. This does not mean that the DFD has lost its usefulness even for new analysis endeavors, and any business analyst is bound to encounter them while reviewing the original design documentation for legacy systems.
Enter Email:
Readers Comments
1 of 6
10/11/2012 8:08 PM
Diagram Elements The diagram elements listed below and in the subsequent worked example are based on the Gane-Sarson symbol set (or notation) for Data Flow Diagrams. There are other symbol sets such as Yourdon-Coad, which comprise the same four element types albeit represented using different shapes. This lozenge shape represents a system Processwhich typically consumes data from an Interfaceor Data Store (see below), transforms it in some way, and then feeds out the end result. to anInterface or Data Store.
Simply Superb...Thanks for sharing. Sanjeet Parthasarathy, Project Manager @ Shoe Mart, United Arab Emirates
Search
This rectangle shape represents an externalInterface, which is any external system or human actor that interacts with our system processes. In some alternative notations theInterface shape may be known as aTerminator, an Input/Output or an Entity.
Podcast
Project Community Recommends

Project Management Methodology and Process An entire Project Management Methodology for Project Managers, including Templates and Case Studies to increase your project success.
A Data Flow line shows data flowing from aProcess to an external Interface or Data Store, or data flowing from an externalInterface or Data Store to a Process. The data flows in the direction of the arrow. A Data Store may represent an entire database or a more specific entity within a database or other persistent data store.
Archives
October 2012 September 2012 August 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 January 2012 December 2011 November 2011 October 2011 September 2011 August 2011
While this table of diagram elements is informative, the only way to truly appreciate the role of the Data Flow Diagram is via a concrete worked example. Worked Example The figure below shows a Data Flow Diagram that was drawn in Microsoft Visio using the Gane-Sarson symbol set. A good Data Flow Diagram should be easy to comprehend and intuitively obvious to the lay person; ideal for reviewing with non-technical project stakeholders. So take time to interpret the diagram yourself, and then read the description that follows.
2 of 6
10/11/2012 8:08 PM
This worked example DFD comprises five processes, four external interfaces / actors, and two data stores. It is not meant to be an exhaustive representation of the data flows in a banking system, but sufficiently comprehensive to give a good feel for how a DFD might be constructed A Bank Manager actor provides New account details to the Open Account process which results inCustomer details being persisted in the Customer Database data store and Account details being persisted in the Account Database data store. Although we have used the phrase results in as part of this explanation, the DFD implies no such cause and effect; all it shows is that the Open Accountprocess can read in data from the Bank Manager interface and write out data to the Customer Database and Account Database data stores in no particular order. A Customer actor using the Online Banking Login process must provide some data in the form of a set of Login credentials such as a user name and password. A Customer actor can receive a Money amount from the Withdraw process and can supply aMoney amount to the Deposit process; in either case causing (although this causation cannot be explicitly modeled) an Account balance update to the Account Database data store. A Customer actor can initiate the Transfer Funds process, to which he or she must provide anAccount destination and money amount. The Transfer Funds process can send a Money amount to another bank via the Other Bank interface. Just like the Customer actor, a Third Party actor can make use of the Deposit process (but obviously not the Withdraw process) by supplying a Money amount. Tips and Tricks Although our focus is on computer systems and software implementations, the DFD has wider uses in modelling non-computerised company processes and exchanges of information. The abstract symbol set could be used to model manual processes and physical data stores such as a filing cabinet. But were computer analysts, right? Data flows between external interfaces and data stores should not be shown, for the simple reason that these are considered to be external and out of scope. The analyst should have no knowledge of the interconnections between external entities. Notice how in the worked example, when modeling the data flow from the Customer to the Loginprocess we chose to label the data flow with the phrase Login credentials rather than (for example)username and password. This gives us some flexibility in defining elsewhere what the required login credentials are without invalidating the diagram. In the future we may require the customer to supply an email address and PIN in order to log in. Note, however, that this is a personal preference and some analysts may prefer to be absolutely explicit when labeling data flows. The external interfaces and actors in this DFD correspond with those shown on the Context Diagram in the previous article, so all we have really done here is to decompose the all-encompassing Bank System process from the Context Diagram into a set of internal processes for specific tasks. We have defined these processes with a view to
3 of 6
10/11/2012 8:08 PM
making each one a discrete use case on a UML Use Case Diagram, with each data flow between an Interface and a Process in this diagram suggesting an association between an Actor and a Use Case. This is not obligatory and is merely a suggestion for aiding traceability between the various systems analysis diagrams and artifacts. The DFD might also drive the creation of another UML diagram: the UML Activity Diagram which would show the order in which the Processes to be re-branded as Activities would be performed. This would resolve the problem of the DFD show what data is exchanged but not when. Next Stop: the Entity-Relationship Diagram The Data Flow Diagram focuses on the data that flows between system processes and external interfaces, and alludes to the fact that some data are persisted in data stores. The data store that has persisted (pun intended) for longest, i.e. has stood the test of time, is the relational database. So in the next article well look at how to model a relational database structure using an Entity-Relationship Diagram. Author : Tony Loton Author & Self-Publisher As a former IT consultant and consultancy practice manager, Tony has published many IT feature articles and books including the most recent UML Software Design with Visual Studio 2010 Article source: http://www.modernanalyst.com/Resources/Articles/tabid/115/articleType /ArticleView/articleId/2015/Data-Flow-Diagram-with-Examples-Tips.aspx
Further Reading
How to Effectively Engage Requirement Contributors to Achieve Project Success Five Keys to Succeeding With Big Data Verifying Requirements Documentation Is a Systems Analyst a Business Analyst? Planning a project meeting Oracle Launching Big Data, in-Memory Appliances
Comments
Add a comment...
Comment
Facebook social plugin
Powered by Facebook Comments

Tags: Business Analysis, Business Analysis - Net, communication, diagram, Management, methodology, Modern Analyst This entry was posted on May 8, 2012 at 2:00 pm and is filed under Articles, Business Analysis, Communication, Management, Methodology, On the Net. You can follow any responses to this entry through the RSS 2.0 feed.
Leave a Reply
Your email address will not be published. Required fields are marked * Name * Email * Website Comment *
4 of 6
10/11/2012 8:08 PM
Time-Stingy Project Leaders
Requirements Completeness Checklist
Team Kick-Off Quick Reference Guide
Unrealistic Management Expectations
Guest Writers Want to share your knowledge and inspire others?
5 of 6
10/11/2012 8:08 PM
LinkedIn Polls
In your experience what makes a really effective knowledge library?

Easy to add content to Advanced search features Advanced retrieval system Has info on experience not just Home | About | Store | Free Stuff | Articles | Contact | Members Area
Copyright 2012 Project Community. All Rights Reserved. Magazine Premium created by Themes by bavotasan.com
6 of 6
10/11/2012 8:08 PM

Data Flow Diagram With Examples & Tips

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Flow Diagram With Examples & Tips

Uploaded by

Copyright:

Available Formats

Data Flow Diagram with Examples & Tips

Install Adobe PDF Reader