Context is king: The developer perspective on the usage of static analysis tools
Authors:
- 1 March 2018
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 38-49
Abstract
Automatic static analysis tools (ASATs) are tools that support automatic code quality evaluation of software systems with the aim of (i) avoiding and/or removing bugs and (ii) spotting design issues. Hindering their wide-spread acceptance are their (i) high false positive rates and (ii) low comprehensibility of the generated warnings. Researchers and ASATs vendors have proposed solutions to prioritize such warnings with the aim of guiding developers toward the most severe ones. However, none of the proposed solutions considers the development context in which an ASAT is being used to further improve the selection of relevant warnings. To shed light on the impact of such contexts on the warnings configuration, usage and adopted prioritization strategies, we surveyed 42 developers (69% in industry and 31% in open source projects) and interviewed 11 industrial experts that integrate ASATs in their workflow. While we can confirm previous findings on the reluctance of developers to configure ASATs, our study highlights that (i) 71% of developers do pay attention to different warning categories depending on the development context, and (ii) 63% of our respondents rely on specific factors (e.g., team policies and composition) when prioritizing warnings to fix during their programming. Our results clearly indicate ways to better assist developers by improving existing warning selection and prioritization strategies.Keywords
This publication has 35 references indexed in Scilit:
- Enriching in-IDE process information with fine-grained source code history2017
- Tricorder: Building a Program Analysis Ecosystem2015
- Would static analysis tools help developers with code reviews?2015
- Comparing static bug finders and statistical prediction2014
- Guidelines for conducting and reporting case study research in software engineeringEmpirical Software Engineering, 2008
- A Comparative Study of Industrial Static Analysis ToolsElectronic Notes in Theoretical Computer Science, 2008
- A Survey of Automated Techniques for Formal Software VerificationIEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems, 2008
- Predicting accurate and actionable static analysis warnings2008
- Extended static checking for Java2002
- Advances in software inspectionsIEEE Transactions on Software Engineering, 1986