Simplified software inspection process in compliance with international standards

A significant amount of software is developed all over the world by small and medium size software organizations. These organizations do not have enough infrastructures and resources to implement an austere quality plan. Software inspection is a fundamental component of the software quality assurance process. Formal review methods are rigorous and their implementation is cumbersome for small and medium enterprises. In this paper, we have presented a new simplified inspection process which is easy to implement, requires fewer resource and almost no documentation. Also, people who are conducting this inspection need not be present at the same place during most stages of the inspection process. We have also compared this process with IEEE and NASA standards for software inspection and found that it meets almost 99% of both standards. While there has been much research on inspection, little attention is paid towards compliance with international standards. These results could be used as a basis for further research in software inspection and process towards aligning with international standards. This process has been successfully implemented in a CMM level 3 software development organization which is striving to accomplish higher maturity levels to establish at the international level.

[1]  Stefan Biffl,et al.  Investigating the Defect Detection Effectiveness and Cost Benefit of Nominal Inspection Teams , 2003, IEEE Trans. Software Eng..

[2]  Forrest Shull,et al.  Software inspections, reviews & walkthroughs , 2002, ICSE '02.

[3]  Henrik Hedberg,et al.  Introducing the Next Generation of Software Inspection Tools , 2004, PROFES.

[4]  J. Miller,et al.  A Comparison of Tool-Based and Paper-Based Software Inspection , 1998, Empirical Software Engineering.

[5]  Lasse Harjumaa,et al.  The virtual logging meeting: a web-based solution to resource problems in software inspection , 1998 .

[6]  Per Runeson,et al.  A replicated experiment of usage-based and checklist-based reading , 2004 .

[7]  Ronald A. Radice,et al.  High Quality Low Cost Software Inspections , 2001 .

[8]  David Lorge Parnas,et al.  The Role of Inspection in Software Quality Assurance , 2003, IEEE Trans. Software Eng..

[9]  Colin Atkinson,et al.  Generalizing perspective-based inspection to handle object-oriented development artifacts , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[10]  L. G. Votta,et al.  Organizational congestion in large-scale software development , 1994, Proceedings of the Third International Conference on the Software Process. Applying the Software Process.

[11]  Stefan Biffl,et al.  A family of experiments to investigate the effects of groupware for software inspection , 2006, Automated Software Engineering.

[12]  Edward Yourdon,et al.  Structured walkthroughs , 1978 .

[13]  F. MacDonald,et al.  A review of tool support for software inspection , 1995, Proceedings Seventh International Workshop on Computer-Aided Software Engineering.

[14]  Wei-Tek Tsai,et al.  An experimental study of fault detection in user requirements documents , 1992, TSEM.

[15]  Chris Sauer,et al.  Validating the defect detection performance advantage of group designs for software reviews: report of a laboratory experiment using program code , 1997, ESEC '97/FSE-5.

[16]  Harvey P. Siy,et al.  An experiment to assess cost-benefits of inspection meetings and their alternatives: a pilot study , 1996, Proceedings of the 3rd International Software Metrics Symposium.

[17]  James R. Lyle,et al.  A Two-Person Inspection Method to Improve Prog ramming Productivity , 1989, IEEE Transactions on Software Engineering.

[18]  Philip M. Johnson.  An instrumented approach to improving software quality through formal technical review , 1994, Proceedings of 16th International Conference on Software Engineering.

[19]  Thomas Gilb,et al.  Software Inspection , 1994 .

[20]  Lawrence G. Votta,et al.  Does every inspection need a meeting? , 1993, SIGSOFT '93.

[21]  L. L. Tripp,et al.  The application of multiple team inspections on a safety-critical software standard , 1991, [1991 Proceedings] Fourth Software Engineering Standards Application Workshop.

[22]  Stefan Biffl,et al.  Software Reviews: The State of the Practice , 2003, IEEE Softw..

[23]  Michael E. Fagan.  Design and Code Inspections to Reduce Errors in Program Development (Reprint) , 2002, Software Pioneers.

[24]  Adam A. Porter,et al.  Assessing Software Review Meetings: Results of a Comparative Analysis of Two Experimental Studies , 1997, IEEE Trans. Software Eng..

[25]  Oliver Laitenberger,et al.  An encompassing life cycle centric survey of software inspection , 2000, J. Syst. Softw..

[26]  Chris Sauer,et al.  Technical Reviews: A Behaviorally Motivated Program of Research , 2022 .

[27]  Claes Wohlin,et al.  State‐of‐the‐art: software inspections after 25 years , 2002, Softw. Test. Verification Reliab..

[28]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[29]  M. Dyer,et al.  Verification based inspection , 1992, Proceedings of the Twenty-Fifth Hawaii International Conference on System Sciences.

[30]  Lasse Harjumaa,et al.  Using Software Inspection as a Catalyst for SPI in a Small Company , 2004, PROFES.

[31]  Glen W. Russell,et al.  Experience with inspection in ultralarge-scale development , 1991, IEEE Software.

[32]  Craig K. Tyran,et al.  Improving software inspections with group process support , 2002, CACM.

[33]  John C. Knight,et al.  An improved inspection technique , 1993, CACM.

[34]  JefferyRoss,et al.  Validating the defect detection performance advantage of group designs for software reviews , 1997 .

[35]  D. Ross Jeffery,et al.  Comparing inspection strategies for software requirement specifications , 1996, Proceedings of 1996 Australian Software Engineering Conference.

[36]  Bill Brykczynski,et al.  Software inspection : an industry best practice , 1996 .

[37]  Philip M. Johnson,et al.  Does Every Inspection Really Need a Meeting? , 1998, Empirical Software Engineering.

[38]  Oliver Laitenberger,et al.  Evaluating the usefulness and the ease of use of a Web-based inspection data collection tool , 1998, Proceedings Fifth International Software Metrics Symposium. Metrics (Cat. No.98TB100262).

[39]  Bill Brykczynski,et al.  Software inspection : an industry best practice , 1996 .

[40]  Robert G. Ebenau,et al.  Software Inspection Process , 1993 .