@inproceedings {Simula.SE.449,
	title = {Evaluating the Relation Between Coding Standard Violations and Faults Within and Across Software Versions},
	journal = {6th IEEE Working Conference on Mining Software Repositories (MSR)},
	year = {2009},
	pages = {41-51},
	publisher = {IEEE},
	type = {Conference},
	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.},
	keywords = {Conference},
	isbn = {978-1-4244-3493-0},
	author = {Boogerd, Cathal and Moonen, Leon},
	editor = {Jim Whitehead {Godfrey}}
}
@inbook {Simula.SE.683,
	title = {Using Software History to Guide Deployment of Coding Standards},
	booktitle = {Trader: Reliability of high-volume consumer products},
	year = {2009},
	pages = {39-52},
	publisher = {Embedded Systems Institute},
	organization = {Embedded Systems Institute},
	chapter = {4},
	address = {Eindhoven, the Netherlands},
	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. Therefore, we propose to use information from software and issue archives to link standard violations to known bugs. In this chapter we introduce such an approach and apply it to three industrial case studies. Furthermore, we discuss how to use the historical data to address two practical issues in using a coding standard: which rules to adhere to, and how to rank violations of those rules.},
	isbn = {978-90-78679-04-2},
	author = {Boogerd, Cathal and Moonen, Leon},
	editor = {Mathijssen, R.}
}
@inproceedings {Simula.SE.331,
	title = {Assessing the Value of Coding Standards: an Empirical Study},
	journal = {Proceedings of the 24th IEEE International Conference on Software Maintenance (ICSM 2008)},
	year = {2008},
	month = {October},
	pages = {277-286},
	publisher = {IEEE},
	type = {Conference},
	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. Not only can compliance with a set of rules having little impact on the number of faults be considered wasted effort, but it can actually result in an increase in faults, as any modification has a non-zero probability of introducing a fault or triggering a previously concealed one. Therefore, it is important to build a body of empirical knowledge, helping us understand which rules are worthwhile enforcing, and which ones should be ignored in the context of fault reduction. In this paper, we describe two approaches to quantify the relation between rule violations and actual faults, and present empirical data on this relation for the MISRA C 2004 standard on an industrial case study.},
	isbn = {978-1-4244-2613-3},
	author = {Boogerd, Cathal and Moonen, Leon},
	editor = {Mei, Hong and Wong, Kenny}
}
@inproceedings {Simula.SE.333,
	title = {On the Use of Data Flow Analysis in Static Profiling},
	journal = {Proceedings of the Eighth IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2008)},
	year = {2008},
	month = {September},
	pages = {79-88},
	publisher = {IEEE},
	type = {Conference},
	abstract = {Static profiling is a technique that produces estimates of execution likelihoods or frequencies based on source code analysis only. It is frequently used in determining cost/benefit ratios for certain compiler optimizations. In previous work,we introduced a simple algorithm to compute execution likelihoods,based on a control flow graph and heuristic branch prediction. In this paper we examine the benefits of using more involved analysis techniques in such a static profiler. In particular, we explore the use of value range propagation to improve the accuracy of the estimates, and we investigate the differences in estimating execution likelihoods and frequencies.},
	isbn = {978-0-7695-3353-7},
	author = {Boogerd, Cathal and Moonen, Leon},
	editor = {Cordy, James and Zhang, Lu}
}
@inproceedings {Simula.SE.479,
	title = {Prioritizing Software Inspection Results Using Static Profiling},
	journal = {Proceedings Sixth IEEE International Workshop on Source Code Analysis and Manipulation (SCAM)},
	year = {2006},
	month = {sep},
	publisher = {IEEE},
	type = {Conference},
	abstract = {Static software checking tools are useful as an additional automated software inspection step that can easily be integrated in the development cycle and assist in creating secure, reliable and high quality code. However, an often quoted disadvantage of these tools is that they generate an overly large number of warnings, including many false positives due to the approximate analysis techniques. This information overload effectively limits their usefulness. In this paper we present ELAN, a technique that helps the user prioritize the information generated by a software inspection tool, based on a demand-driven computation of the likelihood that execution reaches the locations for which warnings are reported. This analysis is orthogonal to other prioritization techniques known from literature, such as severity levels and statistical analysis to reduce false positives. We evaluate feasibility of our technique using a number of case studies and assess the quality of our predictions by comparing them to actual values obtained by dynamic profiling.},
	author = {Boogerd, Cathal and Moonen, Leon}
}
@inproceedings {Simula.SE.467,
	title = {Ranking Software Inspection Results Using Execution Likelihood},
	journal = {Proceedings Philips Software Conference (PSC)},
	year = {2006},
	month = {nov},
	publisher = {Philips},
	type = {Conference},
	author = {Boogerd, Cathal and Moonen, Leon}
}
