Use of software inspection inputs in practice

The effects in the empirical study of different kinds of inputs on the software inspection process can be classified into explicit inputs and implicit inputs. Explicit inputs are the software artifacts to be inspected, the documentation and inspection aids used by the inspectors. Implicit inputs include inspectors' expertise, norms, beliefs and values.

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

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

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

[4]  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.

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

[6]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

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

[8]  Michael E. Fagan.  Advances in software inspections , 1986, IEEE Transactions on Software Engineering.

[9]  Adam A. Porter,et al.  Quality Time: What Makes Inspections Work? , 1997, IEEE Softw..

[10]  A. Frank Ackerman,et al.  Software inspections: an effective verification process , 1989, IEEE Software.

[11]  Adam A. Porter,et al.  An experiment to assess different defect detection methods for software requirements inspections , 1994, Proceedings of 16th International Conference on Software Engineering.

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

[13]  Raymond Madachy,et al.  Analysis of a successful inspection program , 1993 .

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

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

[16]  Edward F. Weller,et al.  Lessons from three years of inspection data (software development) , 1993, IEEE Software.

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

[18]  Forrest Shull,et al.  The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.

[19]  Khaled El Emam,et al.  Evaluating Capture-Recapture Models with Two Inspectors , 2001, IEEE Trans. Software Eng..

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

[21]  Generator Ground Protection.  An American National Standard , 1985 .

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

[23]  野中 郁次郎,et al.  The Knowledge-Creating Company: How , 1995 .

[24]  B BisantDavid,et al.  A Two-Person Inspection Method to Improve Programming Productivity , 1989 .

[25]  Wei-Tek Tsai,et al.  N-Fold inspection: a requirements analysis technique , 1990, Commun. ACM.

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

[27]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

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