Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

The DOI matches its Crossref record; 23 of the 23 references it cites were found in a registry or an index.

Why don't software developers use static analysis tools to find bugs?

Johnson, Brittany, Song, Yoonki, Murphy-Hill, Emerson, Bowdidge, Robert · 2013 · 2013 35th International Conference on Software Engineering (ICSE)

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

Crossref · 10.1109/icse.2013.6606613

Cites

23 of 23 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

Citations

Cites

Show all 23 references

Research works printed but not linked: 10

  1. 0, KLOCwork inSight
  2. 0, Microsoft Visual Studio
  3. 0, Google CodePro Analytix
  4. robertson, 2004, Impact of interruption style on enduser debugging, Proc CHI, 287
  5. lewis, 1982, Using the "Thinking Aloud" Method in Cognitive Interface Design
  6. 0, Eclipse
  7. gordon, 1998, Coding interview responses, Basic Interviewing Skills Waveland Pr Inc, 183
  8. 0, FindBugs
  9. 0, IntelliJ IDEA
  10. 0, Netbeans

Cited by

See all 568

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

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Why don't software developers use static analysis tools to find bugs? https://app.cochat.ai/papers/10.1109/icse.2013.6606613
The paper
Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R. (2013). Why don't software developers use static analysis tools to find bugs? 2013 35th International Conference on Software Engineering (ICSE). https://doi.org/10.1109/icse.2013.6606613

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.