|18.104.22.168 Software Inspection|
With regard to the planning, no more details are required.
The software inspection meeting begins with the instruction of the participants. In this connection, the participants are introduced by the moderator to the objectives and to the procedure. After that a member of the software inspection team presents the contents of the object to be assessed in a brief and logical way. The individual inspectors react with various necessary questions while being supported by the assessment criteria and possibly also by historical data. The developer plays only a passive role. He is ready to answer questions. Discussions are limited to the identification of faults. The moderator will only interfere if the discussion diverts significantly from the subject or the objective of the software inspection. A person taking minutes makes notes of all detected errors faults. After ending the discussion, the listed faults are presented as a whole and investigated with regard to completeness by all participants together.QA4.2 - Assessment of the Content of the Product and QA 6. It can be applied for all possible objects to be assessed.
|/Fagan, 1976/||/Fagan, 76/ Software Inspection procedure; participating persons; possible applications for Software Inspections|
|/Freedman, 1982/||Description of Software Inspections|
|/IEEE 1028, 1988/||Original Literature|
|/ISO DIS 8402-1, 1991/||ISO Definition of the term "Inspection"|
|/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 Walkthrough (p. 152)
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|