Each
decision
point
asks a question such as "IS A LARGER
THAN B?" or "HAVE ALL
THE CARDS BEEN
DEALT?" The
different branches are marked by YES or NO.
Another
useful symbol is:
CONTINUATION
The
circle
usually
has
a
number inside
it
which corresponds to
a number on
another
page if
the
flowchart
is too large
for a single sheet.
CONNECTOR ARROWS
Flowcharts are most
helpful in designing programs
when they are kept
simple. A cluttered
flowchart is hard to
read and usually isn't
much
more
helpful than
an ordinary written
program list. A good
flowchart is also helpful for
"documentation" to
give
you (or others)
a
picture
of how
the
program works
—
for later on,
when
you've
forgotten.
There are
no hard-and-fast
rules about what goes into a
flowchart and what doesn't. A
flow-
chart is
supposed
to help you . .
.
not be more work than
it's worth. It
helps
you
plan
the
logic of
your
program. When
it stops
helping and makes
you
feel like you're back
in
arts
and crafts
designing mosaics, then
you've
gone as far as
the
flowchart will take you (or
more typically,
you've passed its
point of
usefulness).
Let's look at
some
examples.
Suppose
we want to
grade a
5-question
test by
comparing
each of the students'
answers
with the
correct
answer.
We
will put the
correct
answers in a
DATA statement in the program,
enter
a
students'
answers
through
the keyboard,
compare
(grade)
them,
then print
the % of correct
answers.
This
procedure will be
repeated
until
all
the
students
papers are graded.
142
execution
proceeds.
.
which program
To Next Page
Loading...
