2017 · 28 citations · 12 references
ComputingComputer ScienceMethod ValidationProgramming LanguagesSoftware EngineeringSoftware TestingStatic AnalysisStatic Code AnalysisBug Pattern DetectionSource Code AnalysisStatic Bug DetectionStatic Error Analysis
This paper presents our results from identifying anddocumenting false positives generated by static code analysistools. By false positives, we mean a static code analysis toolgenerates a warning message, but the warning message isnot really an error. The goal of our study is to understandthe different kinds of false positives generated so we can (1)automatically determine if an error message is truly indeed a truepositive, and (2) reduce the number of false positives developersand testers must triage. We have used two open-source tools andone commercial tool in our study. The results of our study haveled to 14 core false positive patterns, some of which we haveconfirmed with static code analysis tool developers.
12
Using Static Analysis to Find Bugs
Nathaniel Ayewah, William Pugh, David Hovemeyer et al. · IEEE Software · 2008 · 522 citations
Computing, Computer Science, Secure Software Development +14
Evaluating static analysis defect warnings on production software
Nathaniel Ayewah, William Pugh, J. David Morgenthaler et al. · 2007 · 214 citations
Encyclopedia of computer science
Choice Reviews Online · 1993 · 205 citations