Android Code Smells: From Introduction to ...
Type de document :
Compte-rendu et recension critique d'ouvrage
Titre :
Android Code Smells: From Introduction to Refactoring
Auteur(s) :
Habchi, Sarra [Auteur]
University of Luxembourg [Luxembourg]
Moha, Naouel [Auteur]
Université du Québec à Montréal = University of Québec in Montréal [UQAM]
Rouvoy, Romain [Auteur]
Institut universitaire de France [IUF]
Self-adaptation for distributed services and large software systems [SPIRALS]
University of Luxembourg [Luxembourg]
Moha, Naouel [Auteur]
Université du Québec à Montréal = University of Québec in Montréal [UQAM]
Rouvoy, Romain [Auteur]
Institut universitaire de France [IUF]
Self-adaptation for distributed services and large software systems [SPIRALS]
Titre de la revue :
Journal of Systems and Software
Éditeur :
Elsevier
Date de publication :
2021-07
ISSN :
0164-1212
Discipline(s) HAL :
Informatique [cs]/Génie logiciel [cs.SE]
Informatique [cs]/Informatique mobile
Informatique [cs]/Informatique mobile
Résumé en anglais : [en]
Object-oriented code smells are well-known concepts in software engineering that refer to bad design and development practices commonly observed in software systems. With the emergence of mobile apps, new classes of code ...
Lire la suite >Object-oriented code smells are well-known concepts in software engineering that refer to bad design and development practices commonly observed in software systems. With the emergence of mobile apps, new classes of code smells have been identified by the research community as mobile-specific code smells. These code smells are presented as symptoms of important performance issues or bottlenecks. Despite the multiple empirical studies about these new code smells, their diffuseness and evolution along change histories remains unclear. We present in this article a large-scale empirical study that inspects the introduction, evolution, and removal of Android code smells. This study relies on data extracted from 324 apps, a manual analysis of 561 smell-removing commits, and discussions with 25 Android developers. Our findings reveal that the high diffuseness of mobile-specific code smells is not a result of releasing pressure. We also found that the removal of these code smells is generally a side effect of maintenance activities as developers do not refactor smell instances even when they are aware of them.Lire moins >
Lire la suite >Object-oriented code smells are well-known concepts in software engineering that refer to bad design and development practices commonly observed in software systems. With the emergence of mobile apps, new classes of code smells have been identified by the research community as mobile-specific code smells. These code smells are presented as symptoms of important performance issues or bottlenecks. Despite the multiple empirical studies about these new code smells, their diffuseness and evolution along change histories remains unclear. We present in this article a large-scale empirical study that inspects the introduction, evolution, and removal of Android code smells. This study relies on data extracted from 324 apps, a manual analysis of 561 smell-removing commits, and discussions with 25 Android developers. Our findings reveal that the high diffuseness of mobile-specific code smells is not a result of releasing pressure. We also found that the removal of these code smells is generally a side effect of maintenance activities as developers do not refactor smell instances even when they are aware of them.Lire moins >
Langue :
Anglais
Vulgarisation :
Non
Collections :
Source :
Fichiers
- http://arxiv.org/pdf/2010.07121
- Accès libre
- Accéder au document
- 2010.07121
- Accès libre
- Accéder au document
- document
- Accès libre
- Accéder au document
- 2010.07121.pdf
- Accès libre
- Accéder au document