MétaCan
Menu
Back to cohort
Record W4405868299 · doi:10.1002/spe.3401

Android Source Code Smells: A Systematic Literature Review

2024· article· en· W4405868299 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSoftware Practice and Experience · 2024
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of New Brunswick
Fundersnot available
KeywordsCode smellCode refactoringAndroid (operating system)Computer scienceSoftware engineeringSoftware qualityCode reviewSoftwareData scienceWorld Wide WebSoftware developmentProgramming languageOperating system

Abstract

fetched live from OpenAlex

ABSTRACT Introduction Modern software developers strive to develop applications that are robust, easy to maintain, and possess high levels of quality. However, code smells can hinder this goal as they are visible signs of underlying issues. Numerous techniques and tools have been proposed for detecting code smells in various contexts and programming languages. Despite this, research on Android‐specific code smells and their impact on external quality attributes is still in its early stages. Objective This study aims to provide a comprehensive summary of state‐of‐the‐art techniques, tools, and approaches used for detecting and refactoring code smells in Android applications. Methodology A systematic literature review was conducted between November 2007 and December 2023, adhering to standard guidelines. In total, 79 primary studies were identified, analyzed, and synthesized. Results A total of 237 code smells were identified using 51 techniques and tools, based on seven distinct approaches. Efficiency was found to be the most affected external quality attribute. The code smell Durable Wakelock was the most studied. Challenges Despite the extensive research, the software engineering community faces numerous challenges. These include a lack of in‐depth investigation into Android‐specific code smells, a limited number of studied quality attributes, insufficient involvement of industry experts in the research process, scarcity of Android‐oriented metrics, and dependence on industry‐exclusive datasets. Future Directions This review suggests potential research directions that are valuable for researchers and practitioners seeking to gain insights into current open research problems in this domain.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.011
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: Systematic review
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.430
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.011
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.003
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.014
GPT teacher head0.311
Teacher spread0.297 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it