1. The programmer narrates, statement by statement, the logic of the
program. During the discourse, other participants should raise questions,
which should be pursued to determine whether errors exist. It
is likely that the programmer, rather than the other team members,
will find many of the errors identified during this narration. In other
words, the simple act of reading aloud a program to an audience seems
to be a remarkably effective error-detection technique.
2. The program is analyzed with respect to checklists of historically
common programming errors (such a checklist is discussed in the
next section).