Code Authorship and Fault-proneness of Open-Source Android Applications

Businge, John; Kawuma, Simon; Khomh, Foutse; Nabaasa, Evarist

doi:10.1145/3127005.3127009

Cited by 16 publications

(5 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Bird et al [10] used code authorship metrics to identify the developer who originated problems in code and also to identify developers to whom fault fixes should be assigned. [17] also report a similar relationship between authorship and faults in Android applications. Overall, there seems to be growing empirical evidence that authors who are actively involved with a piece of code insert fewer faults into that code.…”

Section: Introductionmentioning

confidence: 57%

Fault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projects

Destefanis

Hall

Bowes

2023

Information and Software Technology

View full text Add to dashboard Cite

Section: Introductionmentioning

confidence: 57%

Fault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projects

Destefanis

Hall

Bowes

2023

Information and Software Technology

View full text Add to dashboard Cite

“…From each repository's AndroidManifest.xml file, we extract the app's package name and check its existence on Google Play. In total, we find 7,423 mainline repositories representing an actual Google Play app (Businge et al 2017). 3.…”

Section: Identifying Android Familiesmentioning

confidence: 99%

Reuse and maintenance practices among divergent forks in three software ecosystems

et al. 2022

Self Cite

View full text Add to dashboard Cite

With the rise of social coding platforms that rely on distributed version control systems, software reuse is also on the rise. Many software developers leverage this reuse by creating variants through forking, to account for different customer needs, markets, or environments. Forked variants then form a so-called software family; they share a common code base and are maintained in parallel by same or different developers. As such, software families can easily arise within software ecosystems, which are large collections of interdependent software components maintained by communities of collaborating contributors. However, little is known about the existence and characteristics of such families within ecosystems, especially about their maintenance practices. Improving our empirical understanding of such families will help build better tools for maintaining and evolving such families. We empirically explore maintenance practices in such fork-based software families within ecosystems of open-source software. Our focus is on three of the largest software ecosystems existence today: , , and . We identify and analyze software families that are maintained together and that exist both on the official distribution platform (Google play, , and ) as well as on GitHub , allowing us to analyze reuse practices in depth. We mine and identify 38 software families, 526 software families, and 8,837 software families from the ecosystems of , , and , to study their characteristics and code-propagation practices. We provide scripts for analyzing code integration within our families. Interestingly, our results show that there is little code integration across the studied software families from the three ecosystems. Our studied families also show that techniques of direct integration using git outside of GitHub is more commonly used than GitHub pull requests. Overall, we hope to raise awareness about the existence of software families within larger ecosystems of software, calling for further research and better tools support to effectively maintain and evolve them.

show abstract

“…Businge et al [30] studied the relationship between code authorship and fault-proneness of android applications, they investigated whether android applications with few major contributor have more or less faults compared to application with larger number of developer that do minor contributions. They discovered that android applications with higher level of code authorship among contributors experience fewer faults.…”

Section: Related Workmentioning

confidence: 99%

An Empirical Study of Bugs in Eclipse Stable Internal Interfaces

Kawuma¹,

Nabaasa²

2022

Preprint

Self Cite

View full text Add to dashboard Cite

The Eclipse framework is a popular and widely used framework that has been evolving for over a decade. The framework provides both stable interfaces (APIs) and unstable interfaces (non-APIs). Despite being discouraged by Eclipse, application developers often use non-APIs which cause their systems to fail when ported to new framework releases. Previous studies showed that applications using relatively old non-APIs are more likely to be compatible with new releases compared to the ones that used newly introduced non-APIs. Furthermore, from our previous study about the stability of Eclipse internal interfaces, we discovered that there exist 327K stable non-API methods as the Eclipse framework evolves. In the same study, we recommended that 327K stable non-API methods can be used by Eclipse interface providers as possible candidates for promotion to stable interfaces. However since non-APIs are unsupported and considered to be immature i.e. can contain bugs, to this end there exist a need to first investigate the stable non-APIs for possible bugs before they can be promoted to APIs. In this study, we empirically investigated the stable non-API for possible bugs using Sonarqube software quality tool. We discovered that over 79.8% classes containing old stable non-APIs methods have zero bugs. These results can be used by both interface providers and users as a starting point to analyze which interfaces are well tested and also estimate how much work could be involved when performing bug fixing for a given eclipse release.

show abstract

Code Authorship and Fault-proneness of Open-Source Android Applications

Cited by 16 publications

References 20 publications

Fault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projects

Fault-insertion and fault-fixing behavioural patterns in Apache Software Foundation Projects

Reuse and maintenance practices among divergent forks in three software ecosystems

An Empirical Study of Bugs in Eclipse Stable Internal Interfaces

Contact Info

Product

Resources

About