[pdf][proceedings]

As increasingly complex software is developed every day, a growing number of companies use static analysis tools to reason about program properties ranging from simple coding style rules to more advanced software bugs, to multi-tier security vulnerabilities. While increasingly complex analyses are created, developer support must also be updated to ensure that the tools are used to their best potential. Past research in the usability of static analysis tools has primarily focused on usability issues encountered by software developers, and the causes of those issues in analysis tools. In this article, we adopt a more user-centered approach, and aim at understanding why software developers use analysis tools, which decisions they make when using those tools, what they look for when making those decisions, and the motivation behind their strategies. This approach allows us to derive new tool requirements that closely support software developers (e.g., systems for recommending warnings to fix that take developer knowledge into account), and also open novel avenues for further static-analysis research such as collaborative user interfaces for analysis warnings.

@ARTICLE{9124719,
  author={Nguyen Quang Do, Lisa and Wright, James R. and Ali, Karim},
  journal={IEEE Transactions on Software Engineering}, 
  title={Why Do Software Developers Use Static Analysis Tools? A User-Centered Study of Developer Needs and Motivations}, 
  year={2022},
  volume={48},
  number={3},
  pages={835-847},
  doi={10.1109/TSE.2020.3004525}
}