A large-scale study of usability criteria addressed by static analysis tools

Visualization of object-oriented software in a city metaphor: Comprehending the implemented variability and its technical debt

“…It results that the only missing information is the number of overloads of methods and constructors. Although such metrics could be provided by static analysis tools, Nachtigall et al [114] recently studied how 46 such tools fulfill 36 usability criteria from the literature, revealing that they are majoritarily limited regarding their usability and capacity to limit false positives. We therefore collected this information in a CSV file to complete the baseline, thus ensuring their correctness and mitigating the risk that subjects will lose time manipulating additional tools.…”

A Study Of Civil Engineering Education At Singapore Nanyang Technology University And At The University Of Florida

“…In this study, we first collected 148 QA tools supporting Java language from 6 references [17,23,33,35,57,58] including GitHub, OWASP, NIST, Kompar, and Wikipedia, which is collected by snowballing the tool set from [31]. Then, we investigated the characteristics of the tools and defined 6 selection criteria as follows.…”

“…Braga et al analyzed the effectiveness of static analysis tools in identifying cryptography-related vulnerabilities [4,5]. Furthermore, there exist many studies focusing on usability research regarding static analysis tools [11,21,31,36,54,55] and analysis of static analysis tools for smart contracts [12,16].…”

“…An increasing number of software bugs have been discovered during operations, resulting in severe consequences, including massive economic loss and even endangering human lives [19,27,38,60]. Given the importance of software code quality, quality assurance (QA) tools have been widely used due to their low cost, convenience, and ability to find bugs [3,31].…”