Evaluating DFD Quality

With reference to assignments 8 and 9, what characteristics does an analyst (you) examine when evaluating DFD quality? (1500 words)

Before going to the point I will just discuss about what Data Flow Diagram is:

As information moves through software, it is modified by a series of transformations. A data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The basic form of a data flow diagram, also known as a data flow graph or a bubble chart, is illustrated in Figure 1. The data flow diagram may be used to represent a system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as well as information flow modeling. In so doing, it satisfies the second operational analysis principle (i.e., creating a functional model). A level 0 DFD, also called a fundamental system model or a context model, represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively. Additional processes (bubbles) and information flow paths are represented as the level 0 DFD is partitioned to reveal more detail. For example, a level 1 DFD might contain five or six bubbles with interconnecting arrows. Each of the processes represented at level 1 is a sub function of the overall system depicted in the context model. As has been noted earlier, each of the bubbles may be refined or layered to depict more detail.

As information moves through software, it is modified by a series of transformations. A data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The basic form of a data flow diagram, also known as a data flow graph or a bubble chart. The data flow diagram may be used to represent a system or software at any level of abstraction. In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as well as information flow modeling. In so doing, it satisfies the second operational analysis principle (i.e., creating a functional model). A level 0 DFD, also called a fundamental system model or a context model, represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows, respectively. Additional processes (bubbles) and information flow paths are represented as the level 0 DFD is partitioned to reveal more detail. For example, a level 1 DFD might contain five or six bubbles with interconnecting arrows. Each of the processes represented at level 1 is a sub function of the overall system depicted in the context model. As has been noted earlier, each of the bubbles may be refined or layered to depict more detail.

Data flow diagrams defined

Data flow diagram is a geographical tool that shows, process, flows, stores and external entities in a system. Dataflow diagram shows the transformation of data into a system. DFD has got the following symbols

Process flow diagrams

Process symbol has got the following entities, process number (tells the number of the process), locality (where activity is happening) and a process name

Data flow datagram process symbol rules

• It symbolizes the transformation of data
• There must be data flowing into/out of the process
• Process can have several inputs to it or output to it
• Process with no out becomes a null process

Data store Symbol

Consist of the following entities, data store number and name of data store. The function of data store is to designate the storage of data in a DFD diagram

Rules of Data store

• DFD data store do not by level but they may reappear incase needed
• The symbol and the numbering remain the same

Data flow symbol

Data flow symbol may appear in different shape and they signify the movement of data. They do not signify the movement of people, goods etc

• Doubles arrows signifies that activities occur at the same time which is wrong
• Data flow in is never equal to data flow out

Extended entity symbol

Extended entity is sources and destination of data. This means that source is the origin and destination is the sink of data

Dos and Don’ts of external entity
• External entity never communicate with each other, this signify that there is no need for the process
• External entity should not communicate directly with data store because external entities can be identifier with the record of files and databases

How to develop Logical data flow diagram

Below are the guidelines in developing data flow diagrams
1. Develop a physical DFD
2. Explore the process for more details
3. Maintain consistency between the process
4. Following meaningful leveling convention
5. Ensure that DFD diagrams clarifies what is happening in the system
6. Remember DFD audience
7. Add control on the lower level DFD only
8. Assign meaningful level
9. Evaluate DFD for correctness

Step in drawing DFD diagrams
1. Make a list of all business activities and use it to determine the various external entities, data flows, process and data store
2. Create a context diagram which shows external entity and data flows to and from the system
3. Do not show any detailed process or data store
4. Draw diagram zero or the next level to show process but keep them general. Show data stores and the level
5. Create a child diagram for each of the process in diagram zero
6. Check for errors and make sure the levels you assign to each process and data flow are meaningful
7. Develop a physical DFD diagram from the logical DFD and distinguish between the manual and automated protocol, describe actual files and report by name and controls to indicate when the process are complete or errors occurs
8. Portion the physical DFD by separating or grouping parts of the diagram in order to facilitate programming and implementation

Advantages of data flow diagrams
• It gives further understanding of the interestedness of the system and sub-systems
• It is useful from communicating current system knowledge to the user
• Used as part of the system documentation files
• Dataflow diagram helps to substantiate the logic underlining the dataflow of the organization
• It gives the summary of the system
• DFD is very easy to follow errors and it is also useful for quick reference to the development team for locating and controlling errors

Disadvantages of data flow diagram
• DFD is likely to take many alteration before agreement with the user
• Physical consideration are usually left out
• It is difficult to understand because it ambiguous to the user who have little or no knowledge

So basically, these are the characteristics that a system analyst must have in order to evaluate the Data Flow Diagram with quality. The system analyst must have a good background of what are the systems that existed and he should also be able to identify what are those processes that a system must have with regarding to the goals of the organization. And also, an analyst must gather important information in order to have sufficient information in making the DFD. And he also must have enough background on what is their business processes. Good communication skills as well as good critical thinking. And lastly, being able to adapt to change, as we all know we are in the fast changing world or era. Well, that’s it. These are the characteristics that a good system analyst must have in order to evaluate the DFD with quality.


References:
http://hubpages.com/hub/What-is-a-data-flow-diagram