Computer Software and Programming I-67
outline the general procedure. Since they provide an alternative and visual way of representing the
information flow in a program, program developers often find them very valuable.
The advantages (or the reasons) of using flowcharts as a problem-solving tool are given as follows:
• Makes logic clear: The main advantage of using a flowchart to plan a task is that it provides a pic-
torial representation of the task, which makes the logic easier to follow. The symbols are connected
in such a way that they show the movement (flow) of information through the system visibly. The
steps and how each step is connected to the next can be clearly seen. Even less experienced per-
sonnel can trace the actions represented by a flowchart, that is, flowcharts are ideal for visualizing
fundamental control structures employed in computer programming.
• Communication: Being a graphical representation of a problem-solving logic, flowcharts are
better way of communicating the logic of a system to all concerned. The diagrammatical represen-
tation of logic is easier to communicate to all the interested parties as compared to actual program
code, as the users may not be aware of all the programming techniques and jargons.
• Effective analysis: With the help of a flowchart, the problem can be analysed in an effective way.
This is because the analyzing duties of the programmers can be delegated to other persons, who
may or may not know the programming techniques, as they have a broad idea about the logic.
Being outsiders, they often tend to test and analyse the logic in an unbiased manner.
• Useful in coding: The flowcharts act as a guide or blueprint during the analysis and program
development phases. Once the flowcharts are ready, the programmers can plan the coding process
effectively, as they know where to begin and where to end, making sure that no steps are omitted.
As a result, error-free programs are developed in HLLs and that too at a faster rate.
• Proper testing and debugging: By nature, a flowchart helps in detecting the errors in a program,
as the developers know exactly what the logic should do. Developers can test various data for a
process, so that the program can handle every contingency.
• Appropriate documentation: Flowcharts serve as a good program documentation tool. Since
normally the programs are developed for novice users, they can take the help of the program docu-
mentation to know what the program actually does and how to use the program.
Flowcharts can be used for designing the basic concept of the program in pictorial form but cannot be
used for programming purposes. Some of the limitations of the flowchart are given as follows:
• Complex: The major disadvantage in using flowcharts is that when a program is very large, the
flowcharts may continue for many pages, making them hard to follow. Flowcharts tend to get large
very quickly and it is difficult to follow the represented process. It is also very laborious to draw a
flowchart for a large program. You can very well imagine the nightmare when a flowchart is to be
developed for a program, consisting of thousands of statements.
• Costly: Drawing flowcharts are viable only if the problem-solving logic is straightforward and not
very lengthy. However, if flowcharts are to be drawn for a huge application, the time and the cost
factors of program development may get out of proportion, making it a costly affair.
• Difficult to modify: Due to its symbolic nature, any changes or modification to a flowchart usu-
ally requires redrawing the entire logic again, and redrawing a complex flowchart is not a simple
task. It is not easy to draw thousands of flow lines and symbols along with proper spacing, espe-
cially for a large complex program.
12. List some standard symbols used in flowchart with their description.
Ans: A flowchart is drawn according to the defined rules and using standard flowchart symbols
prescribed by American National Standard Institute (ANSI). Some standard symbols that are frequently
used for drawing flowcharts are shown in Table 4.3.
M04_ITL-ESL4791_01_SE_C04.indd 67 12/22/2012 4:53:45 PM