Flowcharting With the A N S I Standard: A Tutorial
09 <
-1O 3
3:E 7
(-7 E -10 J
7F
(-7(7 ()o Z
F7
FIG. 18. Example of an open and a tight layout of a system chart for the same system
tem chart, even simple straight lines of
flow are difficult to see clearly.
A fifth guideline is to collect incoming
flowlines and outgoing flowhnes so that the
flowlines actually entering and leaving a
processing outhne are kept to the mini-
mum. This is illustrated in Figure 17.
A sixth guideline is to minimize crossing
flowlines. Crossing flowlines can be elimi-
nated by repeating input or output out-
lines with appropriate cross-references as
to source or destination.
A seventh guidehne is to use the spe-
cialized outlines wherever possible (com-
pare Figures 12 and 13). Their use im-
proves the communication value of the
system chart. T h e y are only slightly more
difficult to draw.
An eighth guideline is to use cross-ref-
erencing and annotation generously, but
* 133
not to excess. The more the system chart
can tell the reader qmckly and easily, the
more valuable i.t is. Ways ot providing
cross-referencing and annotation are men-
tioned above.
A ninth guideline is to give particular
attention to the processing that affects
data prior to the time t h a t the data be-
come input to a computer program or run.
These are most often manual operations
and auxiliary operations. Failure to spec-
ify them in full is one of the most common
shortcomings of system charts. (Example:
How did the data get punched into the
cards in the system shown in Figure 19?)
A tenth guidehne is to begin with what
is known and well understood. Prepare the
system chart describing that. Then extend
the system chart in each direction. T h a t is,
for each of the inputs shown, find the
Computing Surveys, Vol. 2, No. 2, June 1970