Software product improvement with inspection. A large-scale experiment on the influence of inspection processes on defect detection in software requirements documents

Biffl, Stefan; Halling, Michael

doi:10.1109/eurmic.2000.874427

Cited by 5 publications

(8 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Cost-Benefit Analysis [132], [151], [171], [227] Not stated [121], [123], [126], [131], [136], [137], [157], [159], [166], [167], [177], [184], [193], [194], [198], [205], [206], [208], [220], [249], [250] 21 of whether the assessed results are in causal relationship with the SPI initiative, is rarely discussed (see Section 3.4.7 for a more detailed discussion).…”

Section: Analysis and Discussionmentioning

confidence: 99%

“…[120], [127]- [129], [131], [137], [138], [141]- [143], [146], [152], [155], [159], [160], [163], [165], [167], [168], [175], [176], [181], [187], [192], [195], [197]- [199], [201]- [204], [211]- [214], [218], [224], [228], [231], [232], [234], [237], [240], [241], [248], [249], [251], [253], [256], [257], [259]- [261], [265], [266] 57 Estimation Accuracy…”

Section: Analysis and Discussionunclassified

See 1 more Smart Citation

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

BACKGROUND-Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE-This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD-The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS-Seven distinct evaluation strategies were identified, whereas the most common one, "Pre-Post Comparison", was applied in 49% of the inspected papers. Quality was the most measured attribute (62%), followed by Cost (41%) and Schedule (18%). Looking at measurement perspectives, "Project" represents the majority with 66%. CONCLUSION-The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that "Pre-Post Comparison" was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.

show abstract

Section: Analysis and Discussionmentioning

confidence: 99%

Section: Analysis and Discussionunclassified

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

show abstract

“…Thus, such common defect types existing in the literature occurs in the studies of Brykczynski (1999;Biffl and Halling, 2000;Laitenberger et al, 2001;Sabaliauskaite et al, 2002a;2004;Thelin et al, 2003;Denger and Paech, 2004;Cox et al, 2004a;Staron et al, 2005;Mohammed et al, 2015). A brief discussion of each study of such techniques/approaches is presented as follows:…”

Section: Research Question 2 (Rq2a and Rq2b)mentioning

confidence: 99%

“…The study performed by Biffl and Halling (2000) experimentally investigated the effect of CBR, SBR and PBR reading techniques and detection of defects involved in quality inspection process. Therefore, obtained results corroborated the effectiveness of such techniques.…”

Section: Research Question 2 (Rq2a and Rq2b)mentioning

confidence: 99%

“…In summary, the studies presented in this section answered RQ2 and provide evidence of the existing inspection techniques or approaches associated with defect types, encompassing studies, such as: (i) several academic validation studies that compare and evaluate the effectiveness of the main inspection techniques (e.g., CBR, PBR, SBR, Ad hoc, among others) in distinct contexts (Biffl and Halling, 2000;Cox et al 2004a;Denger and Paech, 2004;Laitenberger et al, 2001;Mohammed et al, 2015;Sabaliauskaite et al, 2002a;2003;Staron et al, 2005;Thelin et al, 2003); (ii) case studies in industry (Felderer et al, 2014;Ma et al, 2014; and (iii) application and adaptation of systematic classifications such as ODC (Gopinath et al, 2014;Ma et al 2014;.…”

Section: Research Question 2 (Rq2a and Rq2b)mentioning

confidence: 99%

See 1 more Smart Citation

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

OliveiraJr¹,

Geraldi²

2017

Journal of Computer Science

View full text Add to dashboard Cite

Software inspection has been used to guarantee and control the quality of products by detecting defects, which can be spread out throughout the entire software life cycle. Therefore, the main premise is to identify and reduce the number of defect types in software artifacts during inspections. This work focuses on providing an up to dated overview of existing defects in the context of software inspection techniques. A systematic mapping was carried out, from which 2096 primary studies were retrieved and 32 were final selected. From the analysis, classification and aggregation of the retrieved studies, important different defect types were identified. Most studies encompass defect types by means of experiments and proposed techniques and approaches. Thus, as a main result, the identification of several different studies with distinct proposals concerned on defect types is evident. Although researchers have conducted studies over time, a general pattern on the detection of defects could not be established. Therefore, the scenario in which this study was carried out provides researchers with the capability of conducting further research in a motivating and challenging research topic, as well as practitioners with the adoption of empirically evaluated inspection techniques and respective defect types.

show abstract

Using reading techniques to focus inspection performance

Halling¹,

Biffl²,

Grechenig³

et al.

Proceedings 27th EUROMICRO Conference. 2001: A Net Odyssey

Self Cite

View full text Add to dashboard Cite

SofnYare inspection is a quality assurance method to detect defects early during the software development process. For inspection planning there are defect detection techniques, so-called reading techniques, which let the inspection planner focus the effectiveness of individual inspectors on specific sets of defects. For realistic planning it is important to use empirically evaluated defect detection techniques.In this paper we report on the replication of a largescale experiment in an academic environment. The experiment evaluated the efectiveness of defect detection jor inspectors who use a checklist orfocused scenarios on individual and team level.A main finding of the experiments is that the teams were effective to find defects: In both experiments the inspection teams found on average more than 70% ofthe defects in the product. The checklist consistently was overall somewhat more effective on individual level, while the scennrios traded overall defect detection effectiveness for much better effectiveness regarding their target focus, in our case specific parts ofthe documents.Another main result of the study is that scenario-based reading techniques can be used in inspection planning to focus individual performance without signijcant loss of effectiveness on team level.Keywords: S o f i a r e inspection process, defect detection techniques, quality measurement, replicated experiment, empirical sofhvare engineering.

show abstract

Software product improvement with inspection. A large-scale experiment on the influence of inspection processes on defect detection in software requirements documents

Cited by 5 publications

References 14 publications

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

Using reading techniques to focus inspection performance

Contact Info

Product

Resources

About