Framework for the Development of Automated Inspection Tools

Summary In early stage of software development inspection is one of the best method for identifies defects and removing defects. Automated inspections are done with some automated inspection tools. A number of automated inspection tools have been developed to support software inspection. Meanwhile existing automated inspection tools have implemented few set of parameters and software development environment require many parameters for inspection process. In this paper, we describe some common refer tool on the basis of literature also identified parameter and sub parameter of these tools. Then we conduct an industry survey meanwhile we combined both surveys. Then we proposed a framework for the development of automated inspection tools which set of parameters are implemented by automated inspection tools.

[1]  James Miller,et al.  A Comparison of Computer Support Systems for Software Inspection , 2004, Automated Software Engineering.

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

[3]  David Hovemeyer,et al.  Finding bugs is easy , 2004, SIGP.

[4]  John C. Knight,et al.  An Improved Software Inspection Technique and An Empirical Evaluation , 1992 .

[5]  Laurie A. Williams,et al.  Preliminary results on using static analysis tools for software inspection , 2004, 15th International Symposium on Software Reliability Engineering.

[6]  Lasse Harjumaa,et al.  A path to virtual software inspection , 2001, Proceedings Second Asia-Pacific Conference on Quality Software.

[7]  David Hovemeyer,et al.  Experiences Using Static Analysis to Find Bugs , 2008 .

[8]  James Miller,et al.  Further Experiences with Scenarios and Checklists , 1998, Empirical Software Engineering.

[9]  Gérard Memmi,et al.  Scrutiny: A Collaborative Inspection and Review System , 1993, ESEC.

[10]  John C. Knight,et al.  Phased inspections and their implementation , 1991, SOEN.

[11]  Stefan Biffl,et al.  An experiment family to investigate the defect detection effect of tool-support for requirements inspection , 2003, Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717).

[12]  Paul M. Anderson The Use and Limitations of Static-Analysis Tools to Improve Software Quality , 2008 .

[13]  Vahid Mashayekhi,et al.  A Case Study of Distributed, Asynchronous Software Inspection , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[14]  James Miller,et al.  Automated generic support for software inspection , 1997 .

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

[16]  Philip M. Johnson THROUGH A COMPUTER SUPPORTED COLLABORATIVE REVIEW SYSTEM , 1995 .

[17]  Adam A. Porter,et al.  Anywhere, Anytime Code Inspections: Using the Web to Remove Inspection Bottlenecks in Large-Scale Software Development , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[18]  James M. Bieman,et al.  The Effectiveness of Automated Static Analysis Tools for Fault Detection and Refactoring Prediction , 2009, 2009 International Conference on Software Testing Verification and Validation.

[19]  John D. Ferguson,et al.  ASSISTing Management Decisions in the Software Inspection Process , 2002, Inf. Technol. Manag..

[20]  Philip M. Johnson,et al.  Assessing software review meetings: A controlled experimental study using CSRS , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[21]  J. David Morgenthaler,et al.  Evaluating static analysis defect warnings on production software , 2007, PASTE '07.

[22]  Giuseppe Scanniello,et al.  Evaluating distributed inspection through controlled experiments , 2009, IET Softw..

[23]  Giuseppe Scanniello,et al.  Assessing the Effectiveness of a Distributed Method for Code Inspection: A Controlled Experiment , 2007, International Conference on Global Software Engineering (ICGSE 2007).

[24]  Susanne Döpke,et al.  The Language Environment , 1992 .

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

[26]  Kai Petersen,et al.  Benefits and limitations of automated software testing: Systematic literature review and practitioner survey , 2012, 2012 7th International Workshop on Automation of Software Test (AST).

[27]  David Lorge Parnas,et al.  Active design reviews: principles and practices , 1985, ICSE '85.

[28]  Fraser Macdonald,et al.  Computer Supported Software Inspection , 1999 .

[29]  J. Miller,et al.  ASSIST - a tool to support software inspection , 1999, Inf. Softw. Technol..

[30]  James Miller,et al.  A process for asynchronous software inspection , 1997, Proceedings Eighth IEEE International Workshop on Software Technology and Engineering Practice incorporating Computer Aided Software Engineering.

[31]  Philip Johnson,et al.  Exploring the effectiveness of formal technical review factors with csrs, a collaborative software review system , 1996 .

[32]  Vahid Mashayekhi,et al.  SuiteSound: A System for Distributed Collaborative Multimedia , 1993, IEEE Trans. Knowl. Data Eng..

[33]  Filippo Lanubile,et al.  Tool support for geographically dispersed inspection teams , 2003, Softw. Process. Improv. Pract..

[34]  Marco Tulio Valente,et al.  Static correspondence and correlation between field defects and warnings reported by a bug finding tool , 2011, Software Quality Journal.

[35]  James Miller,et al.  Automating the software inspection process , 1996, Automated Software Engineering.

[36]  Laurie A. Williams,et al.  On the value of static analysis for fault detection in software , 2006, IEEE Transactions on Software Engineering.

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

[38]  Adam E. Irgon,et al.  Knowledge-Based Code Inspection with ICICLE , 1992, IAAI.

[39]  Ilkka Tervonen,et al.  Support for Quality-Based Design and Inspection , 1996, IEEE Softw..

[40]  Wei-Tek Tsai,et al.  Distributed, collaborative software inspection , 1993, IEEE Software.

[41]  Peng Li,et al.  A comparative study on software vulnerability static analysis techniques and tools , 2010, 2010 IEEE International Conference on Information Theory and Information Security.

[42]  Vahid Mashayekhi,et al.  CAIS: collaborative asynchronous inspection of software , 1994, SIGSOFT '94.

[43]  Gerald M. Weinberg,et al.  Handbook of Walkthroughs, Inspections, and Technical Reviews: Evaluating Programs, Projects, and Products , 1990 .

[44]  Adam A. Porter,et al.  Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment , 1995, IEEE Trans. Software Eng..

[45]  Marco Torchiano,et al.  Quantitative Assessment of the Impact of Automatic Static Analysis Issues on Time Efficiency , 2011 .

[46]  Laurence Brothers,et al.  ICICLE: groupware for code inspection , 1990, CSCW '90.

[47]  Laurence Brothers,et al.  ICICLE: Intelligent code inspection in a C language environment , 1990, Proceedings., Fourteenth Annual International Computer Software and Applications Conference.

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

[49]  S. Biffl,et al.  Groupware Support for Software Requirements Inspection , 2001 .

[50]  J. Miller,et al.  An empirical incremental approach to tool evaluation and improvement , 2000, J. Syst. Softw..

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

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

[53]  Michael B. Spring,et al.  Shared defect detection: the effects of annotations in asynchronous software inspection , 2000 .

[54]  James Miller,et al.  A software inspection process definition language and prototype support tool , 1997, Softw. Test. Verification Reliab..

[55]  Sami Kollanus,et al.  Survey of Software Inspection Research , 2009 .

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

[57]  Richard Lippmann,et al.  Testing static analysis tools using exploitable buffer overflows from open source code , 2004, SIGSOFT '04/FSE-12.

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

[59]  Marco Torchiano,et al.  An empirical validation of FindBugs issues related to defects , 2011 .

[60]  Alok Mishra,et al.  A Software Inspection Process for Globally Distributed Teams , 2010, OTM Workshops.

[61]  Sarah Smith Heckman,et al.  A Model Building Process for Identifying Actionable Static Analysis Alerts , 2009, 2009 International Conference on Software Testing Verification and Validation.

[62]  Robert L. Glass,et al.  Software Testing and Industry Needs , 2006, IEEE Softw..

[63]  Jan Jürjens,et al.  Comparing Bug Finding Tools with Reviews and Tests , 2005, TestCom.

[64]  James Miller,et al.  A Software Inspection Process Definition Language and Prototype Support Tool , 1997, Softw. Test. Verification Reliab..

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

[66]  Takuya Yamashita,et al.  Evaluation of Jupiter: A Lightweight Code Review Framework , 2006 .