Software inspection - a blend of discipline and flexibility

Software engineering staff understand software inspection as a rather formal and disciplined process in general. Unfortunately this formality also detracts from its popularity among software practitioners. If we could add flexibility in the form of virtual meetings, for example, we could remove the barriers to including inspection in the development process. The present paper discusses alternative forms of inspection which provide discipline and flexibility on different scales and allow companies to choose an appropriate inspection method. We also introduce an inspection tool for increased flexibility.

[1]  Lasse Harjumaa,et al.  A WWW-based tool for software inspection , 1998, Proceedings of the Thirty-First Hawaii International Conference on System Sciences.

[2]  Michael E. Fagan.  Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[3]  J. B. Iniesta.  A Tool And A Set Of Metrics To SupportTechnical Reviews , 1970 .

[4]  Wolfgang Appelt,et al.  The BSCW system: a WWW-based application to support cooperation of distributed groups , 1996, Proceedings of WET ICE '96. IEEE 5th Workshop on Enabling Technologies; Infrastucture for Collaborative Enterprises.

[5]  Ilkka Tervonen.  MONITORING SOFTWARE INSPECTIONS WITH PRESCRIPTIVE METRICS , 1998 .

[6]  Robert B. Grady,et al.  Key lessons in achieving widespread inspection use , 1994, IEEE Software.

[7]  Philip M. Johnson,et al.  Improving Software Quality through Computer Supported Collaborative Review , 1993, ECSCW.

[8]  Philip M. Johnson.  Reengineering inspection , 1998, CACM.

[9]  Swu Yih,et al.  Prescriptive metrics for software quality assurance , 1994, Proceedings of 1st Asia-Pacific Software Engineering Conference.

[10]  Peter J. Middleton,et al.  Software Inspection , 1994, J. Inf. Technol..

[11]  Tim Berners-Lee,et al.  WWW: Past, Present, and Future , 1996, Computer.