TUTCRIS - Tampereen teknillinen yliopisto

TUTCRIS

Prioritizing corrective maintenance activities for android applications: An industrial case study on android crash reports

Tutkimustuotosvertaisarvioitu

Standard

Prioritizing corrective maintenance activities for android applications : An industrial case study on android crash reports. / Lenarduzzi, Valentina; Stan, Alexandru Cristian; Taibi, Davide; Venters, Gustavs; Windegger, Markus.

Software Quality: Methods and Tools for Better Software and Systems - 10th International Conference, SWQD 2018, Proceedings. Springer-Verlag Berlin Heidelberg, 2018. s. 133-143 (Lecture Notes in Business Information Processing; Vuosikerta 302).

Tutkimustuotosvertaisarvioitu

Harvard

Lenarduzzi, V, Stan, AC, Taibi, D, Venters, G & Windegger, M 2018, Prioritizing corrective maintenance activities for android applications: An industrial case study on android crash reports. julkaisussa Software Quality: Methods and Tools for Better Software and Systems - 10th International Conference, SWQD 2018, Proceedings. Lecture Notes in Business Information Processing, Vuosikerta. 302, Springer-Verlag Berlin Heidelberg, Sivut 133-143, INTERNATIONAL CONFERENCE ON SOFTWARE QUALITY, 1/01/00. https://doi.org/10.1007/978-3-319-71440-0_8

APA

Lenarduzzi, V., Stan, A. C., Taibi, D., Venters, G., & Windegger, M. (2018). Prioritizing corrective maintenance activities for android applications: An industrial case study on android crash reports. teoksessa Software Quality: Methods and Tools for Better Software and Systems - 10th International Conference, SWQD 2018, Proceedings (Sivut 133-143). (Lecture Notes in Business Information Processing; Vuosikerta 302). Springer-Verlag Berlin Heidelberg. https://doi.org/10.1007/978-3-319-71440-0_8

Vancouver

Lenarduzzi V, Stan AC, Taibi D, Venters G, Windegger M. Prioritizing corrective maintenance activities for android applications: An industrial case study on android crash reports. julkaisussa Software Quality: Methods and Tools for Better Software and Systems - 10th International Conference, SWQD 2018, Proceedings. Springer-Verlag Berlin Heidelberg. 2018. s. 133-143. (Lecture Notes in Business Information Processing). https://doi.org/10.1007/978-3-319-71440-0_8

Author

Lenarduzzi, Valentina ; Stan, Alexandru Cristian ; Taibi, Davide ; Venters, Gustavs ; Windegger, Markus. / Prioritizing corrective maintenance activities for android applications : An industrial case study on android crash reports. Software Quality: Methods and Tools for Better Software and Systems - 10th International Conference, SWQD 2018, Proceedings. Springer-Verlag Berlin Heidelberg, 2018. Sivut 133-143 (Lecture Notes in Business Information Processing).

Bibtex - Lataa

@inproceedings{17f18dc920f645b0ab0cf585ad2d9ac7,
title = "Prioritizing corrective maintenance activities for android applications: An industrial case study on android crash reports",
abstract = "Context: Unhandled code exceptions are often the cause of a drop in the number of users. In the highly competitive market of Android apps, users commonly stop using applications when they find some problem generated by unhandled exceptions. This is often reflected in a negative comment in the Google Play Store and developers are usually not able to reproduce the issue reported by the end users because of a lack of information. Objective: In this work, we present an industrial case study aimed at prioritizing the removal of bugs related to uncaught exceptions. Therefore, we (1) analyzed crash reports of an Android application developed by a public transportation company, (2) classified uncaught exceptions that caused the crashes; (3) prioritized the exceptions according to their impact on users. Results: The analysis of the exceptions showed that seven exceptions generated 70{\%} of the overall errors and that it was possible to solve more than 50{\%} of the exceptions-related issues by fixing just six Java classes. Moreover, as a side result, we discovered that the exceptions were highly correlated with two code smells, namely “Spaghetti Code” and “Swiss Army Knife”. The results of this study helped the company understand how to better focus their limited maintenance effort. Additionally, the adopted process can be beneficial for any Android developer in understanding how to prioritize the maintenance effort.",
keywords = "Continuous monitoring, Software quality, Technical debt",
author = "Valentina Lenarduzzi and Stan, {Alexandru Cristian} and Davide Taibi and Gustavs Venters and Markus Windegger",
note = "EXT={"}Lenarduzzi, Valentina{"} jufoid=71106",
year = "2018",
month = "1",
doi = "10.1007/978-3-319-71440-0_8",
language = "English",
isbn = "9783319714394",
series = "Lecture Notes in Business Information Processing",
publisher = "Springer-Verlag Berlin Heidelberg",
pages = "133--143",
booktitle = "Software Quality",

}

RIS (suitable for import to EndNote) - Lataa

TY - GEN

T1 - Prioritizing corrective maintenance activities for android applications

T2 - An industrial case study on android crash reports

AU - Lenarduzzi, Valentina

AU - Stan, Alexandru Cristian

AU - Taibi, Davide

AU - Venters, Gustavs

AU - Windegger, Markus

N1 - EXT="Lenarduzzi, Valentina" jufoid=71106

PY - 2018/1

Y1 - 2018/1

N2 - Context: Unhandled code exceptions are often the cause of a drop in the number of users. In the highly competitive market of Android apps, users commonly stop using applications when they find some problem generated by unhandled exceptions. This is often reflected in a negative comment in the Google Play Store and developers are usually not able to reproduce the issue reported by the end users because of a lack of information. Objective: In this work, we present an industrial case study aimed at prioritizing the removal of bugs related to uncaught exceptions. Therefore, we (1) analyzed crash reports of an Android application developed by a public transportation company, (2) classified uncaught exceptions that caused the crashes; (3) prioritized the exceptions according to their impact on users. Results: The analysis of the exceptions showed that seven exceptions generated 70% of the overall errors and that it was possible to solve more than 50% of the exceptions-related issues by fixing just six Java classes. Moreover, as a side result, we discovered that the exceptions were highly correlated with two code smells, namely “Spaghetti Code” and “Swiss Army Knife”. The results of this study helped the company understand how to better focus their limited maintenance effort. Additionally, the adopted process can be beneficial for any Android developer in understanding how to prioritize the maintenance effort.

AB - Context: Unhandled code exceptions are often the cause of a drop in the number of users. In the highly competitive market of Android apps, users commonly stop using applications when they find some problem generated by unhandled exceptions. This is often reflected in a negative comment in the Google Play Store and developers are usually not able to reproduce the issue reported by the end users because of a lack of information. Objective: In this work, we present an industrial case study aimed at prioritizing the removal of bugs related to uncaught exceptions. Therefore, we (1) analyzed crash reports of an Android application developed by a public transportation company, (2) classified uncaught exceptions that caused the crashes; (3) prioritized the exceptions according to their impact on users. Results: The analysis of the exceptions showed that seven exceptions generated 70% of the overall errors and that it was possible to solve more than 50% of the exceptions-related issues by fixing just six Java classes. Moreover, as a side result, we discovered that the exceptions were highly correlated with two code smells, namely “Spaghetti Code” and “Swiss Army Knife”. The results of this study helped the company understand how to better focus their limited maintenance effort. Additionally, the adopted process can be beneficial for any Android developer in understanding how to prioritize the maintenance effort.

KW - Continuous monitoring

KW - Software quality

KW - Technical debt

U2 - 10.1007/978-3-319-71440-0_8

DO - 10.1007/978-3-319-71440-0_8

M3 - Conference contribution

SN - 9783319714394

T3 - Lecture Notes in Business Information Processing

SP - 133

EP - 143

BT - Software Quality

PB - Springer-Verlag Berlin Heidelberg

ER -