What is a Flowchart?
A flowchart is generally defined as the graphical representation of any algorithm with the use of standard symbols.
Well, a flowchart is also a pictorial/ diagrammatic representation of an algorithm using various shapes like boxes.
It Facilitates visual communications between business executives and programmers with ease.
Well, flowcharts are helpful while explaining the program to others which has to be documented for complex programs.
You may also like: Difference Between Compiler, Interpreter, and Assembler
Pros of Flowchart:
- Flowcharts are regarded as a suitable way of communicating to make understandable representations between programmers and business people.
- So, What flowchart does is; provide the descriptions of algorithms, the ideas, and the logic to any other users, students, etc.
- Flowchart presents the overview of entire problems and the algorithm steps with solutions
- So, in this way, the problems can be analyzed much more efficiently.
- The flowchart provides the proper documentation to execute in an algorithm
- It helps the programmers who will take part in re-updating the features in future
Cons of Flowchart:
When the features and the ideas to be integrated into the program gets heavy and expand, the difficulty of logic to understanding the flowchart also gets difficult
Complex in Modification:
If the program needs changes and modification then, it is more likely to redraw the flowchart completely from the beginning itself.
Guidelines to follow in Flowchart
- Flowcharts should be started from the top of the page and flow down and to the right.
Only standard flowcharting symbols should be used.
- There should be a start and stop on every flowchart.
The flowchart should be clear, neat, and easy to follow. There should be no ambiguity in understanding the flowchart.
- The direction of the flow line of a procedure or system should be from left to right or top to bottom.
- Only one flow line should emerge from a process symbol.
- Only one flow line should enter a decision symbol, but two or three flow lines, one for each possible answer, can leave the decision symbol.
- Only one flow line is used in conjunction with a terminal (Start and Stop) symbol.
- The contents of each symbol should be written legibly. English-like language should be used in flow charts, not specific programming languages.
- If the flowchart becomes complex, connector symbols should be used to reduce the number of flow lines. The intersection of flow lines should be avoided to make the flow chart a more effective and better way of communication.
Examples of Flowchart
Source: A textbook of C-Programming