You are on page 1of 1

134 • Ned Chapin

A67 punched by Personnel Dept from PA file


documents C o u n t m 1 9 7 0 340records,
An example of an elaboration of the
increases about lO%/year standard is the use of a five-pointed star
P43 I-O limited, may be run as backgromld outline to represent data acquired by the
B46 includes date on-line operation of an optical detector
A34 covers only most recent 17 years
of particle tracks in a spark chamber.
Such equipment is not generally available,
P67 CPU IIrmted, updates A34 only wher~ B46
provides new data-may be run any number and hence the standard provides no spe-
of times on same data
cialized outline. The basic input-output
GRAPH m on printer
outline is applicable, and hence no special-
FIG. 19. Example of speclahzed wordingwithin ized outline is really necessary.
the outhnes of a system chart
Flow Diagram Conventions
processing that produces it and what its Function. The flow diagram describes
input is. Then, regarding those inputs as the algorithm for transforming input data
outputs, continue the procedure for each of structures into output data structures. As
those inputs. The same can be done in the such, the primary emphasis is upon depict-
other flow direction for the outputs. In this ing the sequence of operations that tell
way the system chart can be extended to how data are transformed. The secondary
cover the entire system, as well as cover- emphasis is upon identifying the portions
ing this system's tie-in with other systems. of the data structures affected and the
Typically, particular attention is needed operations performed. Questions of media
to the manual and auxihary processing of or equipment typically become trivial.
data in the system. Since commonly the operations to trans-
An eleventh guideline is to make no form data structures consist of long se-
violations of the standard, and to shun quences of actions, the character of the
deviations. This requires a clear distinction flow diagram differs considerably from
between a violation, a deviation, and an that of the system chart. In the system
elaboration. An example may clarify each. chart, a sandwich rule describes its basic
Using closed arrowheads on flowlines is an structure. No such convement rule serves
example of a violation. Another example in the case of the flow diagram. Since it is
is using a circle with a short right-of-cen- in effect an elaboration and extension of
ter horizontal line touching the bottom what is usually shown as a single outline
center, as an outline for data on punched on a system chart, the flow diagram re-
cards. This is a violation because the quires many more outlines and a much
standard assigns a specffic significance to more extensive presentation of details than
such a circle, and provides a specific outline does the system chart.
for data on punched cards. The general character, therefore, of a
Three examples of deviations from the flow diagram is of a sequence of alternat-
standard are provided by IBM [14]. IBM ing flowline and process outlines. Some-
advances an outline for "keying." This is a where in the early portion of this sequence
serious deviation since the standard al- will usually appear one or more input-out-
ready provides two outlines for data from put outlines to indicate the input of a data
key-driven equipment, or its operation. structure. Near the end of the sequence
These are the manual input (on-line) and will usually appear one or more input-
the manual operation (off-line). IBM ad- output outlines to indicate the output of a
vances an outline for a "transmittal tape." data structure.
This is a kind of document. The standard Because of their greater length, the flow
provides an outline for documents gener- diagram must be broken into parts, as a
ally. IBM advances an outline for an "off- practical matter. For this reason, con-
page connector." The standard provides a nector usage and cross-referencing become
connector outline and specifies the use of important considerations in the creating
cross-references to indicate the location. and readmg of flow diagrams.

Computing Surveys, Vol. 2, No 2, June 1970

You might also like