In-process evaluation for software inspection and test

Abstract

The goal of software inspection and test is to reduce the expected cost of software failure over the life of a product. This paper extends the use of defect higgers, the eventsthat 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 shills 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 both 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.

What Types of Defects Are Really Discovered in Code Reviews?

“…We recognize the studies by Chillarege et al [18] (elaborated in [16]) and Siy and Votta [67] as the most significant prior works on the qualitative analysis and classification of defects found in code reviews. Chillarege et al created a classification that was used to classify a large amount of defects, which was later extended and utilized in studies by other scholars.…”

“…Defect distribution between functionality and evolvability. Mi is the industrial data, Ms is the student data, Si [67], O [58], So [68], E1 and E2 [25], and C [16], [18] 5.3 Implications…”

Cognitive factors in perspective-based reading (PBR): A protocol analysis study

“…LH1: Defect discovery is based on critical recognition events in the inspection process that rely on domain knowledge and process experience [9].…”

Evaluating the use of model-based requirements verification method: A feasibility study

“…To improve the quality of requirements specifications written in natural language, many approaches have been developed and validated through controlled and case studies (e.g., [24][25][26][27]). Researchers have devoted a considerable effort to developing methods for detecting and removing the early lifecycle faults i.e., mistakes recorded in the requirements and design documents [19][20][21][22].…”