ACM Home Page
Please provide us with feedback. Feedback
Predicting buggy changes inside an integrated development environment
Full text PdfPdf (453 KB)
Source OOPSLA workshop on eclipse technology eXchange archive
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange table of contents
Montreal, Quebec, Canada
Pages 36-40  
Year of Publication: 2007
ISBN:978-1-60558-015-9
Authors
Janaki T. Madhavan  University of California, Santa Cruz, Santa Cruz, CA
E. James Whitehead, Jr.  University of California, Santa Cruz, Santa Cruz, CA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 43,   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/1328279.1328287
What is a DOI?

ABSTRACT

We present a tool that predicts whether the software under development inside an IDE has a bug. An IDE plugin performs this prediction, using the Change Classification technique to classify source code changes as buggy or clean during the editing session. Change Classification uses Support Vector Machines (SVM), a machine learning classifier algorithm, to classify changes to projects mined from their configuration management repository. This technique, besides being language independent and relatively accurate, can (a) classify a change immediately upon its completion and (b) use features extracted solely from the change delta (added, deleted) and the source code to predict buggy changes. Thus, integrating change classification within an IDE can predict potential bugs in the software as the developer edits the source code, ideally reducing the amount of time spent on fixing bugs later. To this end, we have developed a Change Classification plugin for Eclipse based on client-server architecture, described in this paper.


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
C. Artho. Jlint - Find bugs in Java programs, 2006.
2
3
 
4
 
5
 
6
 
7
T. Copeland. PMD Applied: Centennial Books. 2005.
8
 
9
 
10
11
 
12
13
 
14
15
 
16
 
17
18
 
19
S. Kim, E. J. Whitehead, Jr., and Y. Zhang. Classifying software changes: Clean or buggy. IEEE Trans. Softw. Engin., in review. Manuscript available at http://www.cs.ucsc.edu/~ejw/papers/cc.pdf.
 
20
V. Livshits. Turning Eclipse against itself: Finding bugs in eclipse code using lightweight static analysis. Eclipsecon '05 Research Exchange, March 2005.
 
21
A. Mockus and D. M. Weiss. Predicting risk of software changes. Bell Labs Tech. J., 5(2):169--180, April-June 2000.
 
22
 
23
24
 
25
26
 
27
 
28

Collaborative Colleagues:
Janaki T. Madhavan: colleagues
E. James Whitehead, Jr.: colleagues