CONTEXT: Automated static analysis (ASA) identifies potential source code anomalies early
in the software development lifecycle that could lead to field failures. Excessive alert …

Automated static analysis can identify potential source code anomalies early in the software
process that could lead to field failures. However, only a small portion of static analysis alerts …

Automatic static analysis tools (ASATs) are instruments that support code quality
assessment by automatically detecting defects and design issues. Despite their popularity …

Static analysis (SA) tools that find bugs by inferring programmer beliefs (eg, FindBugs) are
commonplace in today's software industry. While they find a large number of actual defects …

Static analysis tool alerts can help developers detect potential defects in the code early in
the development cycle. However, developers are not always able to respond to the alerts …

Benchmarks provide an experimental basis for evaluating software engineering processes
or techniques in an objective and repeatable manner. We present the FAULTBENCH v0. 1 …

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) …

The use of automatic static analysis has been a software engineering best practice for
decades. However, we still do not know a lot about its use in real-world software projects …

Static analysis tools are useful for finding common programming mistakes that often lead to
field failures. However, static analysis tools regularly generate a high number of false …

Automated static analysis tools (ASATs) have become a major part of the software
development workflow. Acting on the generated warnings, ie, changing the code indicated in …