Issue No. 11 - November (1993 vol. 19)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/32.256853
<p>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.</p>
in-process evaluation; software inspection; software testing; expected cost; software failure; defect triggers; test scenarios; program testing; software quality; software reliability
M. Halliday, I. Bhandari, J. Chaar and R. Chillarege, "In-Process Evaluation for Software Inspection and Test," in IEEE Transactions on Software Engineering, vol. 19, no. , pp. 1055-1070, 1993.