Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!uunet!abvax!iccgcc!kambic
From: kambic@iccgcc.decnet.ab.com
Newsgroups: comp.software-eng
Subject: Re: Code inspections
Message-ID: <3108.27aeae3b@iccgcc.decnet.ab.com>
Date: 5 Feb 91 18:08:11 GMT
References: <14964@megatest.UUCP> <40530@genrad.UUCP> <7362@tekchips.LABS.TEK.COM> <29653@mimsy.umd.edu> <349@tivoli.UUCP>
Lines: 24

In article <349@tivoli.UUCP>, alan@tivoli.UUCP (Alan R. Weiss) writes:
> In article <29653@mimsy.umd.edu> cml@tove.cs.umd.edu (Christopher Lott) writes:
>>In article <40530@genrad.UUCP>, mas@genrad.com (Mark A. Swanson) writes:
[...]
> I absolutely agree.  Still, as people get better at inspections,
> the name of the game really IS getting those defect Finds during
> inspections way up.  The trick is to not make it personal, but acknowledge
> that software engineering is iterative and social in nature (see Weinberg,
> Boehm, et. al).
> 
[...]
There seems to have been little discussion in this thread on the training 
required for doing inspections.  Creating the atmosphere for, and then 
running proper inspections takes time, money, training, schedule impact,
and potentially changes in either the psychology and/or staff of  the 
organization.  Are they valuable?  Absolutely.  Are they free?  Not initially.
The resultant value for some organizations has been measured as is part of the 
literature.  IMHO most organizations have to go through some type of 
justification of the value, and should continue to measure the value in
terms of $ and time.

GXKambic
Allen-Bradley
Standard disclaimers.