With regard to the planning, no more details are required.
In the walkthrough meeting, the object to be assessed is discussed by the assessors after an introductory presentation by the developer and evaluated by putting questions to the developer. The evaluation is realized individually while the developer explains the object to be assessed in detail. The processes are simulated in theory by means of examples. Assessment criteria are optional, but they may be helpful. Particularly the developer himself contributes to the troubleshooting in this procedure. The necessity to explain his product to the team usually has the result that he detects most of the faults himself. In case an agreement is not reached between the assessors, the moderator can make a decision. Basically, comments and decisions are specified by the walkthrough team, though. The developer of the object to be assessed neither participates in the comments nor in the decisions. The resulting comments, change proposals, and decisions are documented by a person taking minutes.QA4.2 - Assessment of the Content of the Product can also be used to assess documents containing a flow chart. In particular these are software designs and implementation documents.
|/Freedman, 1982/||Description of Walkthroughs|
|/IEEE 1028, 1988/||Original Literature|
|/Wallmüller, 1990/||Process of a Review (pp. 147-149)|
Selection of the Participants (pp. 149-150)
Reviews in the Development Process (pp. 153-161)
Limitation to the Software Inspection (p. 152)
|This page online GDPA Online Last Updated 07.Feb.2003 by C. Freericks|