Why don't software developers use static analysis tools to find bugs?
The DOI matches its Crossref record; 23 of the 23 references it cites were found in a registry or an index.
Abstract
Using static analysis tools for automating code inspections can be beneficial for software engineers. Such tools can make finding bugs, or software defects, faster and cheaper than manual inspections. Despite the benefits of using static analysis tools to find bugs, research suggests that these tools are underused. In this paper, we investigate why developers are not widely using static analysis tools and how current tools could potentially be improved. We conducted interviews with 20 developers and found that although all of our participants felt that use is beneficial, false positives and the way in which the warnings are presented, among other things, are barriers to use. We discuss several implications of these results, such as the need for an interactive mechanism to help developers fix defects.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“industry reports show that it is difficult to get developers to adopt static analysis in their workflows [5, 11, 30, 34].”
From Position: Vibe Coding Needs Vibe Reasoning: Improving Vibe Coding with Formal Verification (2025) · cites this paper as [11]
Citations
Cites
(2005) · Texas ScholarWorks (Texas Digital Library) · Cited by 1,064
A few billion lines of code later: using static analysis to find bugs in the real world
Bessey, A., Block, K., Chelf, B., Chou, A., Fulton, B., Hallem, S., Henri-Gros, C., Kamsky, A., McPeak, S., & Engler, D. (2010) · Communications of the ACM · doi:10.1145/1646353.1646374 · Cited by 635
Using Static Analysis to Find Bugs
Ayewah, N., Pugh, W., Hovemeyer, D., Morgenthaler, J. D., & Penix, J. (2008) · IEEE Software · doi:10.1109/ms.2008.130 · Cited by 534
Experiences from Conducting Semi-structured Interviews in Empirical Software Engineering Research
Hove, S. E., & Anda, B. (2005) · 11th IEEE International Software Metrics Symposium (METRICS'05) · doi:10.1109/metrics.2005.24 · Cited by 345
Mylar: a degree-of-interest model for IDEs
Kersten, M., & Murphy, G. C. (2005) · Proceedings of the 4th international conference on Aspect-oriented software development · doi:10.1145/1052898.1052912 · Cited by 298
Johnson, S. C., & Hill, M. G. (1978) · Cited by 280
Static analysis tools as early indicators of pre-release defect density
Nagappan, N., & Ball, T. (2005) · Proceedings of the 27th international conference on Software engineering - ICSE '05 · doi:10.1145/1062455.1062558 · Cited by 272
Secure Programming with Static Analysis
Chess, B., & West, J. (2007) · Cited by 224
Refactoring Tools: Fitness for Purpose
Murphy-Hill, E., & Black, A. P. (2008) · IEEE Software · doi:10.1109/ms.2008.123 · Cited by 155
Self-citationAn interactive ambient visualization for code smells
Murphy-Hill, E., & Black, A. P. (2010) · Proceedings of the 5th international symposium on Software visualization · doi:10.1145/1879211.1879216 · Cited by 147
Self-citationAyewah, N., & Pugh, W. (2010) · International Symposium on Software Testing and Analysis · doi:10.1145/1831708.1831738 · Cited by 130
Heckman, S. S., & Williams, L. A. (2008) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1145/1414004.1414013 · Cited by 99
EFindBugs: Effective Error Ranking for FindBugs
Shen, H., Fang, J., & Zhao, J. (2011) · IEEE International Conference on Software Testing, Verification and Validation (ICST) · doi:10.1109/icst.2011.51 · Cited by 74
Impact of interruption style on end-user debugging
Robertson, T. J., Prabhakararao, S., Burnett, M., Cook, C., Ruthruff, J. R., Beckwith, L., & Phalgune, A. (2004) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/985692.985729 · Cited by 71
The Role of Visual Perception in Data Visualization
Dastani, M. M. (2002) · Journal of Visual Languages & Computing · doi:10.1006/jvlc.2002.0235 · Cited by 61
A report on a survey and study of static analysis users
Ayewah, N., & Pugh, W. (2008) · doi:10.1145/1390817.1390819 · Cited by 54
Layman, L. M., Williams, L. A., & Amant, R. S. (2007) · Proceedings of the ... ACM-IEEE International Symposium on Empirical Software Engineering and Measurement/International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2007.11 · Cited by 49
Path projection for user-centered static analysis tools
Khoo, Y. P., Foster, J. S., Hicks, M., & Sazawal, V. (2008) · ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering (PASTE) · doi:10.1145/1512475.1512488 · Cited by 37
Comparing model checking and static program analysis: A case study in error detection approaches
Vorobyon, K., & Krishnan, P. (2010) · e-publications@bond (Bond University) · Cited by 35
Gegick, M., & Williams, L. A. (2007) · International Conference on Internet Monitoring and Protection · doi:10.1109/icimp.2007.46 · Cited by 29
Error reporting with graduated color
Oberg, B., & Notkin, D. S. (1992) · IEEE Software · doi:10.1109/52.168856 · Cited by 20
Modeling and managing risk early in software development
Briand, L., Thomas, W. M., & Hetmanski, C. J. (2002) · doi:10.1109/icse.1993.346056 · Cited by 13
A study on improving static analysis tools: Why are we not using them?
Johnson, B. (2012) · Proceedings/Proceedings - International Conference on Software Engineering · doi:10.1109/icse.2012.6227228 · Cited by 5
Self-citation
Research works printed but not linked: 10
- 0, KLOCwork inSight
- 0, Microsoft Visual Studio
- 0, Google CodePro Analytix
- robertson, 2004, Impact of interruption style on enduser debugging, Proc CHI, 287
- lewis, 1982, Using the "Thinking Aloud" Method in Cognitive Interface Design
- 0, Eclipse
- gordon, 1998, Coding interview responses, Basic Interviewing Skills Waveland Pr Inc, 183
- 0, FindBugs
- 0, IntelliJ IDEA
- 0, Netbeans
Cited by
Deep Learning Based Vulnerability Detection: Are We There Yet?
Chakraborty, S., Krishna, R., Ding, Y., & Ray, B. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2021.3087402 · Cited by 790
“Although studies report some limited case studies on such on finding vulnerabilities in real-world projects, these case studies do not shed light on the false positives and false negatives [1].”
BackgroundLe Goues, C., Pradel, M., & Roychoudhury, A. (2019) · Communications of the ACM · doi:10.1145/3318162 · Cited by 410
“sis are becoming increasingly popular as quality gates in many companies.(7,23) Testing, at multiple levels of system ab-”
BackgroundAnalyzing the State of Static Analysis: A Large-Scale Evaluation in Open Source Software
Beller, M., Bholanath, R., McIntosh, S., & Zaidman, A. (2016) · 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2016.105 · Cited by 219
“Developers might be unaware of these benefits or an overload of warning messages generated by multiple ASATs might cause developers to avoid them [12].”
BackgroundResultHow developers engage with static analysis tools in different contexts
Vassallo, C., Panichella, S., Palomba, F., Proksch, S., Gall, H. C., & Zaidman, A. (2020) · Empirical Software Engineering · doi:10.1007/s10664-019-09750-5 · Cited by 161
Tricorder: Building a Program Analysis Ecosystem
Sadowski, C., Van Gogh, J., Jaspan, C., Soderberg, E., & Winter, C. (2015) · 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering · doi:10.1109/icse.2015.76 · Cited by 145
“High false positive rates, confusing output, and poor integration into the developers’ workflow all contribute to the lack of use in everyday development activities [23], [27].”
BackgroundInfluential
Metadata
- Authors
- Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R.
- Affiliations
- North Carolina State University (US)
- Google (United States) (US)
- Venue
- 2013 35th International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2013-05
- Pages
- 672-681
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W4233410239
- Cited by
- 568
- References
- 23
- Citations by year
- 2026: 58 · 2025: 58 · 2024: 66 · 2023: 73 · 2022: 65 · 2021: 53 · 2020: 46 · 2019: 41 · 2018: 27 · 2017: 38 · 2016: 21 · 2015: 14 · 2014: 5 · 2013: 3
- FWCI
- 11.51
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Keywords
- static analysis tools, software defect detection, bug detection, false positives, developer behavior
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.