Nonexecution-Based Testing

Walkthroughs

Walkthrough is less formal. Usually four to six people are involved: specification team manager and representative, client representative, design team representative, and SQA specialist.

Documents should be distributed before the meeting. Meeting should not last longer than two hours. SQA specialist chairs the meeting because he(she) has the most to lose. Purpose of walkthrough is to detect the fault(s).

Two ways of conducting the walkthrough: participant-driven, or document-driven. The second approach is likely to detect more faults and recommended by IEEE standard for software reviews.

Discussion: Why the walkthrough should not be chaired by the team manager?