Not logged in.

Quick Search - Contribution

Contribution Details

Type Conference or Workshop Paper
Scope Contributions to practice
Published in Proceedings Yes
Title Context Is King: The Developer Perspective on the Usage of Static Analysis Tools
Organization Unit
Authors
  • Carmine Vassallo
  • Sebastiano Panichella
  • Fabio Palomba
  • Sebastian Proksch
  • Andy Zaidman
  • Harald C Gall
Presentation Type paper
Item Subtype Original Work
Refereed Yes
Status Published in final form
Language
  • English
Page Range 38 - 49
Event Title 25th International Conference on Software Analysis, Evolution and Reengineering, SANER 2018
Event Type conference
Event Location Campobasso, Italy
Event Start Date March 20 - 2018
Event End Date March 23 - 2018
Place of Publication Washington, DC, United States
Publisher IEEE Computer Society
Abstract Text 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.
Related URLs
Digital Object Identifier 10.1109/SANER.2018.8330195
Other Identification Number merlin-id:20334
PDF File Download from ZORA
Export BibTeX
EP3 XML (ZORA)