Modelling the ‘hurried’ bug report reading process to summarize bug reports
Modelling the ‘hurried’ bug report reading process to summarize bug reports
复制标题
DOI：
10.1007/s10664-014-9311-2
复制
发表时间：
2012-09
影响因子：
4.1
通讯作者：
Rafael Lotufo;Zeeshan Malik;K. Czarnecki
中科院分区：
文献类型：
--
作者：
Rafael Lotufo;Zeeshan Malik;K. Czarnecki
尽管bug报告是经常被查阅的项目资产，但它们是沟通日志、bug解决的副产品，而不是为了易于遵循而创建的工件。为了方便bug报告消化，我们提出了一个新的，无监督的，bug报告摘要的方法，估计注意力的用户会假设给予不同的句子在一个bug报告，当紧迫的时间。我们提出了三个假设是什么使一个句子相关：讨论经常讨论的话题，被其他句子评估或评估，并保持专注于错误报告的标题和描述。我们的研究结果表明，我们的假设是有效的，因为摘要有多达12%的标准摘要评估指标相比，以前的方法的改进。我们的评估还要求开发人员评估他们为bug报告创建的摘要的质量和有用性。来自开发人员的反馈不仅表明摘要是有用的，而且还指出了这方面的重要要求，以及任何bug摘要方法，并指出了未来工作的方向。
Although bug reports are frequently consulted project assets, they are communication logs, by-products of bug resolution, and not artifacts created with the intent of being easy to follow. To facilitate bug report digestion, we propose a new, unsupervised, bug report summarization approach that estimates the attention a user would hypothetically give to different sentences in a bug report, when pressed with time. We pose three hypotheses on what makes a sentence relevant: discussing frequently discussed topics, being evaluated or assessed by other sentences, and keeping focused on the bug report’s title and description. Our results suggest that our hypotheses are valid, since the summaries have as much as 12 % improvement in standard summarization evaluation metrics compared to the previous approach. Our evaluation also asks developers to assess the quality and usefulness of the summaries created for bug reports they have worked on. Feedback from developers not only shows the summaries are useful, but also points out important requirements for this, and any bug summarization approach, and indicates directions for future work.