IBM 1130 User Manual page 220

Section
30
Subsections Page
40
I
00 03
k. Generate a new program listing after an
appropriate number of cards have been
added to the program. Update the pro-
gram flowchart to reflect the current
status of the program.
1. Keep documentation current. This
eliminates the waste of time and effort
trying to pick up changes during testing
or debugging.
13. Post-test evaluation. Every test session
should be followed by a thorough evaluation:
a. Was the pretest preparation adequate?
b. Were there any areas of preparation
that could be improved to yield a more
effective test?
c. Were there areas of preparation in
which you spent too little?
d. Did the test point up any areas of weak-
ness in the coding? If so, are these types
of errors documented so that stronger
emphasis can be placed on them during
future coding and desk checking?
e. Was each machine session used
effectively?
f. Are there any corrections to the testing
techniques that would make the next test
mbre fruitful?
g. What is the status of each program
tested?
(1) Is it completely tested? That is,
has every program loop been
tested, and do you have any res-
ervations about calling this program
complete?
(2) Is it tested to the stage where the
only changes left are in spacing and
editing of the output data?
(3) Are there logic errors left in this
program?
h. Did the test session achieve its objec-
tives? If not, what adjustments in
present scheduling are necessary?