The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
Le gestionnaire de packages (PM) est crucial pour la plupart des piles technologiques, agissant comme un courtier pour garantir qu'un package de dépendances vérifié est correctement installé, configuré ou supprimé d'une application. La diversité des piles technologiques a conduit à la création de dizaines de PM dotés de diverses fonctionnalités. Bien que notre étude récente indique que les fonctionnalités de gestion des packages de PM sont liées à l'expérience de l'utilisateur final, nous ne savons pas exactement quels sont ces problèmes et quelles informations sont nécessaires pour les résoudre. Dans cet article, nous avons étudié les problèmes de PM rencontrés par les utilisateurs finaux à travers une étude empirique du contenu sur Stack Overflow (SO). Nous avons effectué une analyse qualitative de 1,131 64 questions et de leurs réponses acceptées pour trois PM populaires (c'est-à-dire Maven, npm et NuGet) afin d'identifier les types de problèmes, leurs causes sous-jacentes et leurs résolutions. Nos résultats confirment que les utilisateurs finaux ont des difficultés à utiliser les outils de gestion de projet (environ 72 à XNUMX %). Nous observons que la plupart des problèmes sont soulevés par les utilisateurs finaux en raison du manque d'instructions et de messages d'erreur des outils PM. En termes de résolution de problèmes, nous constatons que le partage de liens externes est la pratique la plus courante pour résoudre les problèmes de PM. De plus, nous observons que les liens pointant vers des ressources utiles (c'est-à-dire des sites Web de documentation officielle, des didacticiels, etc.) sont les plus fréquemment partagés, ce qui indique le potentiel de prise en charge des outils et la capacité de fournir des informations pertinentes aux utilisateurs finaux de PM.
Syful ISLAM
Noakhali Science and Technology University
Raula GAIKOVINA KULA
Nara Institute of Science and Technology
Christoph TREUDE
University of Melbourne
Bodin CHINTHANET
Nara Institute of Science and Technology
Takashi ISHIO
Nara Institute of Science and Technology
Kenichi MATSUMOTO
Nara Institute of Science and Technology
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copier
Syful ISLAM, Raula GAIKOVINA KULA, Christoph TREUDE, Bodin CHINTHANET, Takashi ISHIO, Kenichi MATSUMOTO, "An Empirical Study of Package Management Issues via Stack Overflow" in IEICE TRANSACTIONS on Information,
vol. E106-D, no. 2, pp. 138-147, February 2023, doi: 10.1587/transinf.2022MPP0001.
Abstract: The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2022MPP0001/_p
Copier
@ARTICLE{e106-d_2_138,
author={Syful ISLAM, Raula GAIKOVINA KULA, Christoph TREUDE, Bodin CHINTHANET, Takashi ISHIO, Kenichi MATSUMOTO, },
journal={IEICE TRANSACTIONS on Information},
title={An Empirical Study of Package Management Issues via Stack Overflow},
year={2023},
volume={E106-D},
number={2},
pages={138-147},
abstract={The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.},
keywords={},
doi={10.1587/transinf.2022MPP0001},
ISSN={1745-1361},
month={February},}
Copier
TY - JOUR
TI - An Empirical Study of Package Management Issues via Stack Overflow
T2 - IEICE TRANSACTIONS on Information
SP - 138
EP - 147
AU - Syful ISLAM
AU - Raula GAIKOVINA KULA
AU - Christoph TREUDE
AU - Bodin CHINTHANET
AU - Takashi ISHIO
AU - Kenichi MATSUMOTO
PY - 2023
DO - 10.1587/transinf.2022MPP0001
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E106-D
IS - 2
JA - IEICE TRANSACTIONS on Information
Y1 - February 2023
AB - The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.
ER -