基于迭代Kuhn-Munkres算法的开发者负载规范化：一种优化的分类方法
Developer Load Normalization Using Iterative Kuhn-Munkres Algorithm: An Optimization Triaging Approach
摘要：
错误分类可以定义为将开发人员分配到错误报告的过程。bug分类小组的职责是研究开发人员的概要文件，以便在开发人员和传入的bug报告之间进行适当的匹配。因此，这一过程是问题管理系统中至关重要的一步。事实上，每天提交的bug报告数量正在逐渐增加，这影响了开发人员的工作量。因此，分类团队在分发bug时应该考虑这个因素，因为手动方法，许多开发人员都是负担。特别是，在不考虑工作负载的情况下对bug报告进行分类，不仅会影响开发人员的工作负载，还会导致未解决的bug报告数量的增加。因此，报告的bug的修复时间将相对增加。与其他专注于自动化错误分类而忽略开发人员工作量的研究人员不同，在这项工作中，我们从不同的角度处理分类过程。所提出的方法侧重于如何优化的错误修复时间规范化的开发人员在自动化系统的负载。为了评估我们的工作，我们使用了来自不同bug库的26，317个bug报告。结果表明，我们的工作优于其他系统在优化的错误总修复时间和正常化的开发人员负载。
英文摘要：
Bug triage can be defined as the process of assigning a developer to a bug report. The duty of the bug triage team is to study the developers profiles well in order to make an appropriate match between the developers and the incoming bug reports. Thus, this process is a vital step in issue management system. In fact, the number of bug reports submitted every day is gradually increasing which affects the developer workload. Thus, the triage team should consider this factor in distributing the bugs and because of the manual approach, many developers are burden. In particular, triaging bug reports without considering the workload does not only affect the developers workload but also leads to an increase in the number of unaddressed bug reports. As a result, the fixing time of the reported bugs will relatively increase. Unlike other researchers who focus on automating the bug triage and ignoring the developer workload, in this work, we handle the triaging process from a different perspective. The proposed approach focuses on how to optimize the bug fixing time by normalizing the developer load in an automating system. To evaluate our work, we use 26,317 bug reports from different bug repositories. Results shows that our work outperforms other systems in terms of optimizing the bug total fixing time and normalizing developer load.
机构、总结、中文摘要均由AI分析而来，可能存在错误，请以论文正文为准。
