Evaluating the relation between coding standard violations and faultswithin and across software versions

Authors:
Cathal Boogerd;Leon Moonen
Affiliations:
Software Evolution Research Lab, Delft University of Technology, The Netherlands;Simula Research Laboratory, Norway
Venue:
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Year:
2009

Citing 0
Cited 3

System-specific static code analyses: a case study in the complex embedded systems domain

Software Quality Control
Using automatic static analysis to identify technical debt

Proceedings of the 34th International Conference on Software Engineering
Creating Process-Agents incrementally by mining process asset library

Information Sciences: an International Journal

Quantified Score

Hi-index	0.00

Visualization

Abstract

In spite of the widespread use of coding standards and tools enforcing their rules, there is little empirical evidence supporting the intuition that they prevent the introduction of faults in software. In previous work, we performed a pilot study to assess the relation between rule violations and actual faults, using the MISRA C 2004 standard on an industrial case. In this paper, we investigate three different aspects of the relation between violations and faults on a larger case study, and compare the results across the two projects. We find that 10 rules in the standard are significant predictors of fault location.