A Longitudinal Study of Static Analysis Warning Evolution and the Effects of PMD on Software Quality in Apache Open Source Projects
Alexander Trautsch, Steffen Herbold, Jens Grabowski

TL;DR
This longitudinal study investigates how static analysis warnings evolve in open source projects, focusing on PMD's impact on code quality and warning trends over 17 years.
Contribution
It provides the first empirical analysis of PMD warning trends in open source projects, revealing the effects of coding style changes and PMD's role in software quality.
Findings
Large global warning changes are mainly due to style adjustments.
PMD's presence in build process has minimal impact on warning removal.
PMD presence correlates with improved defect density.
Abstract
Automated static analysis tools (ASATs) have become a major part of the software development workflow. Acting on the generated warnings, i.e., changing the code indicated in the warning, should be part of, at latest, the code review phase. Despite this being a best practice in software development, there is still a lack of empirical research regarding the usage of ASATs in the wild. In this work, we want to study ASAT warning trends in software via the example of PMD as an ASAT and its usage in open source projects. We analyzed the commit history of 54 projects (with 112,266 commits in total), taking into account 193 PMD rules and 61 PMD releases. We investigate trends of ASAT warnings over up to 17 years for the selected study subjects regarding changes of warning types, short and long term impact of ASAT use, and changes in warning severities. We found that large global changes in…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
