The moderator is responsible for ensuring that the discussions proceed
along productive lines and that the participants focus their attention on
finding errors, not correcting them. (The programmer corrects errors after
the inspection session.)
Upon the conclusion of the inspection session, the programmer is given
a list of the errors uncovered. If more than a few errors were found, or if
any of the errors require a substantial correction, the moderator might
make arrangements to reinspect the program after those errors have been
corrected. This subsequent list of errors is also analyzed, categorized, and
used to refine the error checklist to improve the effectiveness of future
inspections.
As stated, this inspection process usually concentrates on discovering
errors, not correcting them. That said, some teams may find that when a
minor problem is discovered, two or three people, including the programmer
responsible for the code, may propose design changes to handle this
special case. The discussion of this minor problem may, in turn, focus
the group’s attention on that particular area of the design. During the discussion
of the best way to alter the design to handle this minor problem,
someone may notice a second problem. Now that the group has seen two
problems related to the same aspect of the design, comments likely will