In-Process Evaluation for Software Inspection and Test

The goal of software inspection and test is to reduce the expected cost of software failure over the life of a product. The authors extend the use of defect triggers, the events that cause defects to be discovered, to help evaluate the effectiveness of inspections and test scenarios. In the case of inspections, the defect trigger is defined as a set of values that associate the skills of the inspector with the discovered defect. Similarly, for test scenarios, the defect trigger values embody the deferring strategies being used in creating these scenarios. The usefulness of triggers in evaluating the effectiveness of software inspections and tests is demonstrated by evaluating the inspection and test activities of some software products. These evaluations are used to point to deficiencies in inspection and test strategies, and to progress made in improving such strategies. The trigger distribution of the entire inspection or test series may then be used to highlight areas for further investigation, with the aim of improving the design, implementation, and test processes. >

[1]  Boris Beizer,et al.  Software testing techniques (2. ed.) , 1990 .

[2]  Inderpal S. Bhandari,et al.  Orthogonal Defect Classification - A Concept for In-Process Measurements , 1992, IEEE Trans. Software Eng..

[3]  Harlan D. Mills,et al.  Structured programming - theory and practice , 1979, The systems programming series.

[4]  Harlan D. Mills,et al.  Certifying the reliability of software , 1986, IEEE Transactions on Software Engineering.

[5]  Edmund B. Daly Management of Software Development , 1977, IEEE Transactions on Software Engineering.

[6]  Robert G. Mays,et al.  Experiences with Defect Prevention , 1990, IBM Syst. J..

[7]  Boris Beizer,et al.  Software Testing Techniques , 1983 .

[8]  John C. Kelly,et al.  An analysis of defect densities found during software inspections , 1992, J. Syst. Softw..

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

[10]  C. V. Ramamoorthy,et al.  Software Reliability—Status and Perspectives , 1982, IEEE Transactions on Software Engineering.

[11]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[12]  Harlan D. Mills,et al.  Management of Software Engineering, The , 1979 .

[13]  W. E. Stephenson An analysis of the resources used in the SAFEGUARD system software development , 1976, ICSE '76.

[14]  S Hekmatpour Experience with evolutionary prototyping in a large software project , 1987, SOEN.

[15]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[16]  Inderpal S. Bhandari,et al.  In-Process Improvement through Defect Data Interpretation , 1994, IBM Syst. J..

[17]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[18]  John D. Musa,et al.  Software reliability - measurement, prediction, application , 1987, McGraw-Hill series in software engineering and technology.

[19]  Ronald A. Radice,et al.  A Programming Process Architecture , 1985, IBM Syst. J..

[20]  Bev Littlewood,et al.  A Bayesian Reliability Growth Model for Computer Software , 1973 .

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

[22]  G. Wenneson Quality assurance software inspections at NASA Ames: Metrics for feedback and modification , 1985 .

[23]  Ronald A. Radice,et al.  Software Engineering: An Industrial Approach , 1988 .

[24]  Watts S. Humphrey,et al.  Characterizing the software process: a maturity framework , 1988, IEEE Software.

[25]  Ram Chillarege,et al.  Defect type and its impact on the growth curve (software development) , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.

[26]  Glenford J. Myers,et al.  Softwear Reliability , 1976 .

[27]  Glenford J. Myers,et al.  Software Reliability: Principles and Practices , 1976 .

[28]  Amrit L. Goel,et al.  Software Reliability Models: Assumptions, Limitations, and Applicability , 1985, IEEE Transactions on Software Engineering.

[29]  Mark Sullivan,et al.  Software defects and their impact on system availability-a study of field failures in operating systems , 1991, [1991] Digest of Papers. Fault-Tolerant Computing: The Twenty-First International Symposium.

[30]  Harlan D. Mills,et al.  Correction to 'Certifying the reliability of software' (Jan. 1986 3-11) , 1989 .

[31]  Barry W. Boehm,et al.  Improving Software Productivity , 1987, Computer.

[32]  David N. Card,et al.  Improving software quality and productivity , 1987 .

[33]  Richard C. Linger,et al.  Cleanroom software engineering for zero-defect software , 1993, Proceedings of 1993 15th International Conference on Software Engineering.