IZDSW Archive: Formal Technical ReviewsIZDSW Archive: Formal Technical ReviewsSome recent publications in this area:
by Stewart Crawford-Hines. This paper was originally published in the conference proceedings of the Fifth International Conference on Software Quality, ASQC, October 1995, pp.73-81.
Historically, much of the discussion around procedural issues of Software Inspections and Technical Reviews has been rather dogmatic. Many have defined a process in their one particular way and preach it as the One True Path from which no one may stray. However, software development organizations are as diverse as the people that make them up. This report attempts to cull out some of the current dogma and explore its roots, to provide a more balanced view in defining a review or inspection process appropriate to an individual development organization.
by Stewart Crawford-Hines. This is currently a working draft. Please send me any comments to improve it!
Peer reviewing of software engineering work-products has received much attention over the past two decades. While the importance of reviews is amply demonstrated, we lack a consensus on one best process. This stems from the observation that optimal varies across organizations, as a function of their developers, managers, and process background. Key processes, therefore, should not be viewed as having ideal, static solutions; they must be flexible and maturing over time. In this paper, a progression of review processes is delineated, each appropriate for organizations of different maturities. Variations influenced by management styles, and implications for process design and ongoing technology transfer are also discussed.