The relationship of code churn and architectural violations in the open source software JabRef

Abstract

The open source application JabRef has been developed since 2003. In 2015, the developers decided to make an architectural refactoring as continued development was deemed too demanding. The developers also introduced Static Architecture Conformance Checking (SACC) to prevent violations to the intended architecture. Measurements mined from source code repositories such as code churn and code ownership has been linked to several problems, for example fault proneness, security vulnerabilities, code smells, and degraded maintainability. The root cause of such problems can be architectural. To determine the impact of the refactoring of JabRef, we measure the code churn and code ownership before and after the refactoring and find that large files with violations had a significantly higher code churn than large files without violations before the refactoring. After the refactoring, the files that had violations show a more normal code churn. We find no such effect on code ownership. We conclude that files that contain violations detectable by SACC methods are connected to higher than normal code churn. CCS CONCEPTS• Software and its engineering → Software architectures; Software verification and validation;

Can I Solve it? Identifying the APIs required to complete OSS tasks

“…JabRef is a mature and active project created in 2003 (migrated to GitHub in 2014), with 15.7k commits, 42 releases, 337 contributors, 2.7k closed issues, and 4.1k closed pull requests. JabRef has also been frequently investigated in scientific studies [32,33,34,35,36]. We chose JabRef as our case study because of these characteristics and because we have access to the project's contributors.…”