ACM Home Page
Please provide us with feedback. Feedback
Evaluating static analysis defect warnings on production software
Full text PdfPdf (171 KB)
Source
Workshop on Program Analysis for Software Tools and Engineering archive
Proceedings of the 7th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering table of contents
San Diego, California, USA
Pages: 1 - 8  
Year of Publication: 2007
ISBN:978-1-59593-595-3
Authors
Nathaniel Ayewah  Univ. of Maryland, College Park, MD
William Pugh  Univ. of Maryland, College Park, MD
J. David Morgenthaler  Google: Inc., Mountain View, MD
John Penix  Google: Inc., Mountain View, MD
YuQian Zhou  Google: Inc., Mountain View, MD
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 26,   Downloads (12 Months): 193,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Static analysis tools for software defect detection are becoming widely used in practice. However, there is little public information regarding the experimental evaluation of the accuracy and value of the warnings these tools report. In this paper, we discuss the warnings found by FindBugs, a static analysis tool that finds defects in Java programs. We discuss the kinds of warnings generated and the classification of warnings into false positives, trivial bugs and serious bugs. We also provide some insight into why static analysis tools often detect true but trivial bugs, and some information about defect warnings across the development lifetime of software release. We report data on the defect warnings in Sun's Java 6 JRE, in Sun's Glassfish JEE server, and in portions of Google's Java codebase. Finally, we report on some experiences from incorporating static analysis into the software development process at Google.


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
A. Almossawi, K. Lim, and T. Sinha. Analysis tool evaluation: Coverity prevent, May 2006. http://www.cs.cmu.edu/ aldrich/courses/654/tools/cure-coverity-06.pdf.
 
2
K. I. Boudnik. Static analyzers comparison, October 2006. http://weblogs.java.net/blog/cos/archive/2006/10/static analyzer.html.
3
 
4
T. Copeland. PMD Applied. Centennial Books, November 2005.
5
6
7
 
8
R. O'Callahan. Static analysis and scary headlines, September 2006. http://weblogs.mozillazine.org/roc/archives/2006/09/static analysis and scary head.html.
 
9
10
 
11
S. Wagner, F. Deissenboeck, M. A. J. Wimmer, and M. Schwalb. An evaluation of bug pattern tools for java, January 2007. unpublished.
 
12
S. Wagner, J. Jurjens, C. Koller, and P. Trischberger. Comparing bug finding tools with reviews and tests. In Proc. 17th International Conference on Testing of Communicating Systems, pages 40--55, 2005.
13

CITED BY  10

Collaborative Colleagues:
Nathaniel Ayewah: colleagues
William Pugh: colleagues
J. David Morgenthaler: colleagues
John Penix: colleagues
YuQian Zhou: colleagues