Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!kodak!ispd-newsserver!ism.isc.com!b1!ico!auto-trol!alesha
From: alesha@auto-trol.com (Alec Sharp)
Newsgroups: comp.software-eng
Subject: Re: Code Inspections
Keywords: Software Process, Inspections, Methods
Message-ID: <1991Jun20.132511.22508@auto-trol.com>
Date: 20 Jun 91 13:25:11 GMT
References: <1991Jun19.163846.7716@cherokee.uswest.com>
Sender: news@auto-trol.com
Organization: Auto-trol Technology Corporation
Lines: 33
Nntp-Posting-Host: server_3-gw

In article <1991Jun19.163846.7716@cherokee.uswest.com> gbeary@cherokee.uswest.com (Greg Beary) writes:
>Does anyone know of any commercially available Code Inspection
>Methodologies. IE. one that defines a process, provides education,
>and provides supports (tools, doc., etc.) for doing Code Inspection. 
>
>There's lots of CASE vendors that provide services/tools for 
>SA/SD, does anyone do something similiar for Code Inspection?
>Any pointers would be welcomed. 
>

The best review process I know of is that described by Freedman and
Weinberg in "Handbook of Inspections, Walkthroughs, and Technical
Reviews", published by Dorset House.  They are also available for
consulting/training on the process.  The book costs $45 and is worth
every penny.

We also require that all new C code lint cleanly before being
reviewed.  We're defining corporate coding standards, and are looking
into CodeCheck from Abraxas Software as a way to ensure that the
standards are met before reviewing the code.

I know that AT&T Bell Labs has a rigorous code review scheme - if you
know anyone there you might try to find out what they do.

alec...



-- 
-----Any resemblance to the views of Auto-trol is purely coincidental-----
alesha@auto-trol.com
Alec Sharp           Auto-trol Technology Corporation
(303) 252-2229       12500 North Washington Street, Denver, CO 80241-2404