Prioritizing Warning Categories by Analyzing Software History

	This Article
	Subscribers, please Login Purchase article: $19 PDF IEEE Xplore Subscribers RSS feed
	Share
	Email this Article to a friend
	Bibliographic References
	ASCII Text BibTex RefWorks Procite/RefMan/Endnote
	Add to:
	Digg Furl Spurl Blink Simpy Google Del.icio.us Y!MyWeb
	Search
	Similar Articles Articles by Sunghun Kim Articles by Michael D. Ernst

Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007)

Minneapolis, Minnesota

May 20-May 26

ISBN: 0-7695-2950-X

	ASCII Text	x
	Sunghun Kim, Michael D. Ernst, "Prioritizing Warning Categories by Analyzing Software History," Mining Software Repositories, International Workshop on, pp. 27, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007), 2007.

	BibTex	x
	@article{ 10.1109/MSR.2007.26, author = {Sunghun Kim and Michael D. Ernst}, title = {Prioritizing Warning Categories by Analyzing Software History}, journal ={Mining Software Repositories, International Workshop on}, volume = {0}, year = {2007}, isbn = {0-7695-2950-X}, pages = {27}, doi = {http://doi.ieeecomputersociety.org/10.1109/MSR.2007.26}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, }

	RefWorks Procite/RefMan/Endnote	x
	TY - CONF JO - Mining Software Repositories, International Workshop on TI - Prioritizing Warning Categories by Analyzing Software History SN - 0-7695-2950-X SP EP A1 - Sunghun Kim, A1 - Michael D. Ernst, PY - 2007 KW - null VL - 0 JA - Mining Software Repositories, International Workshop on ER -

Sunghun Kim, Massachusetts Institute of Technology, USA

Michael D. Ernst, Massachusetts Institute of Technology, USA

DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MSR.2007.26

Automatic bug finding tools tend to have high false positive rates: most warnings do not indicate real bugs. Usually bug finding tools prioritize each warning category. For example, the priority of "overflow" is 1 and the priority of "jumbled incremental" is 3, but the tools? prioritization is not very effective.

In this paper, we prioritize warning categories by analyzing the software change history. The underlying intuition is that if warnings from a category are resolved quickly by developers, the warnings in the category are important. Experiments with three bug finding tools (FindBugs, JLint, and PMD) and two open source projects (Columba and jEdit) indicate that different warning categories have very different lifetimes. Based on that observation, we propose a preliminary algorithm for warning category prioritizing.

Citation:

Sunghun Kim, Michael D. Ernst, "Prioritizing Warning Categories by Analyzing Software History," msr, pp.27, Fourth International Workshop on Mining Software Repositories (MSR'07:ICSE Workshops 2007), 2007

Peer Review Notice | Give Us Feedback

Usage of this product signifies your acceptance of the Terms of Use.