ACM Home Page
Please provide us with feedback. Feedback
Iterative identification of fault-prone binaries using in-process metrics
Full text PdfPdf (555 KB)
Source
ESEM archive
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement table of contents
Kaiserslautern, Germany
SESSION: Faults and failures table of contents
Pages 206-212  
Year of Publication: 2008
ISBN:978-1-59593-971-5
Authors
Lucas Layman  North Carolina State University, Raleigh, NC, USA
Gunnar Kudrjavets  Microsoft Corporation, Redmond, WA, USA
Nachiappan Nagappan  Microsoft Corporation, Redmond, WA, USA
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 105,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1414004.1414038
What is a DOI?

ABSTRACT

Code churn, the amount of code change taking place within a software unit over time, has been correlated with fault-proneness in software systems. We investigate the use of code churn and static metrics collected at regular time intervals during the development cycle to predict faults in an iterative, in-process manner. We collected 159 churn and structure metrics from six, four-month snapshots of a 1 million LOC Microsoft product. The number of software faults fixed during each period is recorded per binary module. Using stepwise logistic regression, we create a prediction model to identify fault-prone binaries using three parameters: code churn (the number of new and changed blocks); class Fan In and class Fan Out (normalized by lines of code). The iteratively-built model is 80.0% accurate at predicting fault-prone and non-fault-prone binaries. These fault-prediction models have the advantage of allowing the engineers to observe how their fault-prediction profile evolves over time.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
4
 
5
 
6
 
7
 
8
J. E. Jackson, A User's Guide to Principal Components. New York: Wiley, 1991.
9
10
 
11
 
12
M. C. Ohlsson, von Mayrhauser, A., McGuire, B., Wohlin, C., "Code Decay Analysis of Legacy Software through Successive Releases," in IEEE Aerospace Conference, 1999, pp. 69--81.
13
 
14
 
15
 
16

Collaborative Colleagues:
Lucas Layman: colleagues
Gunnar Kudrjavets: colleagues
Nachiappan Nagappan: colleagues