MétaCan
Menu
Back to cohort
Record W3094044696 · doi:10.1109/aire51212.2020.00017

Analysis of Compatibility in Open Source Android Mobile Apps

2020· article· en· W3094044696 on OpenAlexaff
Debjyoti Mukherjee, Guenther Ruhe

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsCompatibility (geochemistry)Computer scienceAndroid (operating system)CommitSoftwareWorld Wide WebSoftware engineeringDatabaseOperating systemEngineering

Abstract

fetched live from OpenAlex

Non-functional requirements (NFRs) form an intrinsic part of any software system. Compatibility between versions or different platforms of a software product is a form of NFRs. In this paper, we have studied Compatibility in open-source mobile apps. We are interested in understanding the different aspects of mobile incompatibility, their frequency of occurrence from a user perspective, and how much effort developers have spent on it. We have conducted a study on 40 randomly selected open-source mobile apps from the Google Play Store and have analyzed 258,056 commits (extracted from their version control system) to identify incompatibility issues in apps. We have also studied 205,847 reviews to identify and categorize compatibility requirements from user reviews. Both app commits and app reviews were processed by a pipeline of Natural Language Processing steps. We evaluated the efficiency of four Machine Learning classifiers to analyze compatibility. This was done by classifying commit messages and analyzing user reviews. We observed that the Logistic Regression classifier produced the best overall results. For the same data set, we classified compatibility types. In that case, the Support Vector Machine classifier performed marginally better over the other classifiers. Addressing the relative effort spent on compatibility, we found that 3.16% of the developer's effort is dedicated to compatibility issues. At the same time, we observed that 4.30% of user reviews report compatibility issues in apps. In conclusion, we see more demand for future research on (i)the gap between the time spent by the developers and the frequency of occurrence of compatibility issues, and (ii) the degree of responsiveness on actual user concerns.

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.

How this classification was reachedexpand

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.647
Threshold uncertainty score0.285

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.001
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.036
GPT teacher head0.306
Teacher spread0.270 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations6
Published2020
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207