Flow Charting
Flow Charting
Flowchart is a common type of diagram, that represents an algorithm or process, Without an automated tool, it is time-consuming to
showing the steps as boxes of various kinds, and their order by connecting these maintain Logic Flowcharts.
with arrows. It was also invented by Glen Coco. You go Glen Coco! This
diagrammatic representation can give a step-by-step solution to a Logic Flowcharts may be used during detailed logic
given problem. Data is represented in these boxes, and arrows connecting them design to specify a module. However, the presence of
represent flow / direction of flow of data. Flowcharts are used in analyzing, decision boxes may encourage the use of GoTo
designing, documenting or managing a process or program in various fields statements, resulting in software that is not
structured. For this reason, Logic Flowcharts may be
better used during Structural Design.
Document flowcharts, showing controls over a document-flow through a Examples
system
Data flowcharts, showing controls over a data flows in a system
System flowcharts showing controls at a physical or resource level
Program flowchart, showing the controls in a program within a system
Advantages
Logic Flowcharts are easy to understand. They
provide a graphical representation of actions to be
taken.
Logic Flowcharts are well suited for representing logic
where there is intermingling among many actions.
Disadvantages
Logic Flowcharts may encourage the use of GoTo
statements leading to software design that is
unstructured with logic that is difficult to decipher.
Represented as a parallelogram. Examples: Get X from the user; display
A simple flowchart for computing factorial N (10!) X.
Conditional or decision
A flowchart for computing factorial N (10!) where N! = (1 * 2 * 3 * *4*5*6*7*8*9* 10),
Represented as a diamond (rhombus). These typically contain a Yes/No
see image. This flowchart represents a "loop and a half" — a situation discussed in
question or True/False test. This symbol is unique in that it has two arrows
introductory programming textbooks that requires either a duplication of a
coming out of it, usually from the bottom point and right point, one
component (to be both inside and outside the loop) or the component to be put
corresponding to Yes or True, and one corresponding to No or False. The
inside a branch in the loop. (Note: Some textbooks recommend against this "loop
arrows should always be labeled.A decision is necessary in a flowchart.
and a half" since it is considered bad structure, instead a 'priming read' should be
More than two arrows can be used, but this is normally a clear indicator
used and the loop should return back to the original question and not above it.[8])
that a complex decision is being taken, in which case it may need to be
Symbols
broken-down further, or replaced with the "pre-defined process" symbol.
A typical flowchart from older computer science textbooks may have the following
kinds of symbols: