论文标题

在实践中采用自动错误分配:爱立信的纵向案例研究

Adopting Automated Bug Assignment in Practice: A Longitudinal Case Study at Ericsson

论文作者

Borg, Markus, Jonsson, Leif, Engström, Emelie, Bartalos, Béla, Szabó, Attila

论文摘要

在大型开发项目中,错误报告的持续流入是一个巨大的挑战。受到当代矿业软件存储库的启发,我们设计了一种基于2011 - 2016年机器学习的原型错误分配解决方案。该原型于2017 - 2018年演变成爱立信内部产品TRR。 TRR在没有人工干预的情况下进行的第一个错误分配发生在2019年4月。我们的研究评估了TRR在爱立信的工业背景下的采用。此外,我们研究了1)TRR在现场的表现,2)TRR对爱立信提供了什么价值,以及3)TRR如何影响工作方式。我们进行了一项工业案例研究,结合了与TRR利益相关者的访谈,Sprint计划会议的会议记录以及错误跟踪数据。数据分析包括主题分析,描述性统计和贝叶斯因果分析。 TRR现在是错误分配过程的合并部分。考虑到电信堆栈的抽象水平,高级模块更为正面,而低级模块则经历了一些缺点。平均而言,TRR自动分配了30%的传入错误报告,精度为75%。自动路由TRS在爱立信内的21%左右得到解决,TRR为经验丰富的工程师节省了很多小时的工作。采用TRR的间接影响包括过程改进,过程意识,沟通的提高和更高的工作满意度。 TRR节省了在爱立信的时间,但是与其他公司报告的类似努力相比,自动化错误分配的采用更为复杂。我们主要将差异归因于组织和复杂产品的较大尺寸。成功采用的主要促进者包括逐步介绍,产品冠军和仔细的利益相关者分析。

The continuous inflow of bug reports is a considerable challenge in large development projects. Inspired by contemporary work on mining software repositories, we designed a prototype bug assignment solution based on machine learning in 2011-2016. The prototype evolved into an internal Ericsson product, TRR, in 2017-2018. TRR's first bug assignment without human intervention happened in April 2019. Our study evaluates the adoption of TRR within its industrial context at Ericsson. Moreover, we investigate 1) how TRR performs in the field, 2) what value TRR provides to Ericsson, and 3) how TRR has influenced the ways of working. We conduct an industrial case study combining interviews with TRR stakeholders, minutes from sprint planning meetings, and bug tracking data. The data analysis includes thematic analysis, descriptive statistics, and Bayesian causal analysis. TRR is now an incorporated part of the bug assignment process. Considering the abstraction levels of the telecommunications stack, high-level modules are more positive while low-level modules experienced some drawbacks. On average, TRR automatically assigns 30% of the incoming bug reports with an accuracy of 75%. Auto-routed TRs are resolved around 21% faster within Ericsson, and TRR has saved highly seasoned engineers many hours of work. Indirect effects of adopting TRR include process improvements, process awareness, increased communication, and higher job satisfaction. TRR has saved time at Ericsson, but the adoption of automated bug assignment was more intricate compared to similar endeavors reported from other companies. We primarily attribute the difference to the very large size of the organization and the complex products. Key facilitators in the successful adoption include a gradual introduction, product champions, and careful stakeholder analysis.

扫码加入交流群

加入微信交流群

微信交流群二维码

扫码加入学术交流群,获取更多资源