Making defect-finding tools work for you

Proceedings - International Conference on Software Engineering

Volumn 2, Issue , 2010, Pages 99-108

  Nanda, Mangala Gowri ^a   Gupta, Monika ^a   Sinha, Saurabh ^a   Chandra, Satish ^b   Schmidt, David ^c   Balachandran, Pradeep ^d  

^a IBM RESEARCH   (United States)

^b IBM T J WATSON RESEARCH CENTER   (United States)

^c IBM   (United States)

^d IBM INDIA RESEARCH LAB   (India)

Author keywords

defect differencing; defect merging; defect prioritization; defect views; static analysis portal

Indexed keywords

ANALYSIS TOOLS; EARLY DETECTION; FALSE POSITIVE; HIGH COSTS; PRIORITIZATION; RETURN ON INVESTMENTS; TRUE POSITIVE;

COMPUTER SOFTWARE SELECTION AND EVALUATION; MERGING; PROGRAM DEBUGGING; SOFTWARE ENGINEERING; SOFTWARE TESTING; STATIC ANALYSIS;

DEFECTS;

EID: 77954718653     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1810295.1810310     Document Type: Conference Paper

References (14)

1. N. Ayewah, D. Hovemeyer, J. D. Morgenthaler, J. Penix, and W. Pugh. Experiences using static analysis to find bugs. IEEE Software, 25(5):22-29, Sept./Oct. 2008.
2. N. Ayewah and W. Pugh. A report on a survey and study of static analysis users. In Proceedings of the 2008 Workshop on Defects in Large Software Systems, pages 1-5, July 2008.
3. N. Ayewah, W. Pugh, J. D. Morgenthaler, J. Penix, and Y. Zhou. Evaluating static analysis defect warnings on production software. In Proceedings of 7th ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering, pages 1-8, June 2007.
4. T. Copeland. PMD applied. Centennial Books, 2005.
5. Coverity. http://www.coverity.com.
6. C. Flanagan, K. R. M. Leino, M. Lillibridge, G. Nelson, J. B. Saxe, and R. Stata. Extended static checking for Java. In Proceedings of the ACM SIGPLAN Conference on Programming Language Design and Implementation, pages 234-245, June 2002.
7. E. Geay, E. Yahav, and S. Fink. Continuous code-quality assurance with SAFE. In Proceedings of ACM SIGPLAN Workshop on Partial Evaluation and Program Manipulation, pages 145-149, Jan. 2006.
8. D. Hovemeyer and W. Pugh. Finding bugs is easy. ACM SIGPLAN Notices (Proceedings of Onward! at OOPSLA 2004), 39(10):92-106, Dec. 2004.
9. C. Jaspan, I.-C. Chen, and A. Sharma. Understanding the value of program analysis tools. In Proceedings of the 22nd ACM SIGPLAN Conference on Object Oriented Programming Systems, Languages, and Applications, pages 963-970, Oct. 2007.
10. JLint. http://artho.com/jlint.
11. S. Kim and M. Ernst. Which warnings should I fix first? In Proceedings of the 6th joint meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering, pages 45-54, Sept. 2007.
12. M. G. Nanda and S. Sinha. Accurate interprocedural null-dereference analysis for Java. In Proceedings of the 31st International Conference on Software Engineering, pages 133-143, May 2009.
13. J. R. Ruthruff, J. Penix, J. D. Morgenthaler, S. Elbaum, and G. Rothermel. Predicting accurate and actionable static analysis warnings: An experimental approach. In Proceedings of the 30th International Conference on Software Engineering, pages 341-350, May 2008.
14. S. Wagner, J. Jrjens, C. Koller, and P. Trischberger. Comparing bug finding tools with reviews and tests. In Proceedings 17th International Conference on Testing of Communicating Systems, volume 3502 of Lecture Notes in Computer Science, pages 40-55, June 2005.