2010•Research Repository (Delft University of Technology)Open access

Focusing Automatic Code Inspections

Cathal Boogerd

Open full text 38 citations

Abstract

Automatic Code Inspection tools help developers in early detection of defects in software. A well-known drawback of many automatic inspection approaches is that they yield too many warnings and require a clearer focus. In this thesis, we provide such focus by proposing two methods to prioritize inspection results, based on the execution likelihood and the historical fault likelihood of warnings. We describe both methods in detail, and evaluate them on various open-source and industry projects.

Open-access reader

About this research paper

What this paper is about

Automatic Code Inspection tools help developers in early detection of defects in software. A well-known drawback of many automatic inspection approaches is that they yield too many warnings and require a clearer focus. In this thesis, we provide such focus by proposing two methods to prioritize inspection results, based on the execution likelihood and the historical fault likelihood of warnings. We describe both methods in detail, and evaluate them on various open-source and industry projects.

Why it matters

OpenAlex reports 38 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Automatic Code Inspection tools help developers in early detection of defects in software. A well-known drawback of many automatic inspection approaches is that they yield too many warnings and require a clearer focus. In this thesis, we provide such focus by proposing two methods to prioritize inspection results, based on the execution likelihood and the historical fault likelihood of warnings. We describe both methods in detail, and evaluate them on various open-source and industry projects.

Key concepts: Software inspection, Computer science, Focus (optics), Software engineering, Software, Code (set theory), Source code, Data mining

Related papers

Back to paper searchBrowse research topicsOriginal source
Focusing Automatic Code Inspections — Research Paper | ScholarLens