On the Survival of Android Code Smells in the Wild
Document type :
Communication dans un congrès avec actes
Title :
On the Survival of Android Code Smells in the Wild
Author(s) :
Habchi, Sarra [Auteur]
Self-adaptation for distributed services and large software systems [SPIRALS]
Rouvoy, Romain [Auteur]
Self-adaptation for distributed services and large software systems [SPIRALS]
Institut universitaire de France [IUF]
Moha, Naouel [Auteur]
Laboratory for Research on Technology for ECommerce [LATECE Laboratory - UQAM Montreal]
Self-adaptation for distributed services and large software systems [SPIRALS]
Rouvoy, Romain [Auteur]
Self-adaptation for distributed services and large software systems [SPIRALS]
Institut universitaire de France [IUF]
Moha, Naouel [Auteur]
Laboratory for Research on Technology for ECommerce [LATECE Laboratory - UQAM Montreal]
Scientific editor(s) :
Denys Poshyvanyk
Ivano Malavolta
Ivano Malavolta
Conference title :
MOBILESoft 2019 - 6th IEEE/ACM International Conference on Mobile Software Engineering and Systems
City :
Montréal
Country :
Canada
Start date of the conference :
2019-05-25
English keyword(s) :
Mobile apps
Android
Change history
Index Terms-Mobile apps
code smells
Android
Change history
Index Terms-Mobile apps
code smells
HAL domain(s) :
Informatique [cs]/Informatique mobile
Informatique [cs]/Informatique ubiquitaire
Informatique [cs]/Génie logiciel [cs.SE]
Informatique [cs]/Informatique ubiquitaire
Informatique [cs]/Génie logiciel [cs.SE]
English abstract : [en]
The success of smartphones and app stores have contributed to the explosion of the number of mobile apps proposed to end-users. In this very competitive market, developers are rushed to regularly release new versions of ...
Show more >The success of smartphones and app stores have contributed to the explosion of the number of mobile apps proposed to end-users. In this very competitive market, developers are rushed to regularly release new versions of their apps in order to retain users. Under such pressure, app developers may be tempted to adopt bad design or implementation choices, leading to the introduction of code smells. Mobile-specific code smells represent a real concern in mobile software engineering. Many studies have proposed tools to automatically detect their presence and quantify their impact on performance. However, there remains—so far—no evidence about the lifespan of these code smells in the history of mobile apps. In this paper, we present the first large-scale empirical study that investigates the survival of Android code smells. This study covers 8 types of Android code smells, 324 Android apps, 255k commits, and the history of 180k code smell instances. Our study reports that while in terms of time Android code smells can remain in the codebase for years before being removed, it only takes 34 effective commits to remove 75% of them. Also, Android code smells disappear faster in bigger projects with higher releasing trends. Finally, we observed that code smells that are detected and prioritised by linters tend to disappear before other code smells.Show less >
Show more >The success of smartphones and app stores have contributed to the explosion of the number of mobile apps proposed to end-users. In this very competitive market, developers are rushed to regularly release new versions of their apps in order to retain users. Under such pressure, app developers may be tempted to adopt bad design or implementation choices, leading to the introduction of code smells. Mobile-specific code smells represent a real concern in mobile software engineering. Many studies have proposed tools to automatically detect their presence and quantify their impact on performance. However, there remains—so far—no evidence about the lifespan of these code smells in the history of mobile apps. In this paper, we present the first large-scale empirical study that investigates the survival of Android code smells. This study covers 8 types of Android code smells, 324 Android apps, 255k commits, and the history of 180k code smell instances. Our study reports that while in terms of time Android code smells can remain in the codebase for years before being removed, it only takes 34 effective commits to remove 75% of them. Also, Android code smells disappear faster in bigger projects with higher releasing trends. Finally, we observed that code smells that are detected and prioritised by linters tend to disappear before other code smells.Show less >
Language :
Anglais
Peer reviewed article :
Oui
Audience :
Internationale
Popular science :
Non
Collections :
Source :
Files
- https://hal.inria.fr/hal-02059097/document
- Open access
- Access the document
- https://hal.inria.fr/hal-02059097/document
- Open access
- Access the document
- https://hal.inria.fr/hal-02059097/document
- Open access
- Access the document
- document
- Open access
- Access the document
- main.pdf
- Open access
- Access the document