paperbot · PL 论文追踪

全部论文 待读 收藏

P2 DRMiner: Extracting Latent Design Rationale from Jira Issue Logs

DRMiner:从 Jira 问题日志中提取潜在设计理由
ASE Proceedings of the 39th IEEE/ACM International Conference on Automated Software Engineering2024匹配度 2/10 · 该论文属于软件工程中的设计理由挖掘,聚焦从 Jira 日志抽取设计备选方案与论证,与用户关注的形式化/静态分析、浮点程序分析、贝叶斯程序分析以及 LLM 与程序分析交叉等核心方向没有直接关联。虽然其“缺乏基准”的动机与用户对重要场景 benchmark 的兴趣略有共鸣,但主题明显偏离。引用 5 inbox
Jiuang Zhao, Zitian Yang, Li Zhang, Xiaoli Lian, Donghao Yang, Xin Tan
crossref: 2026-09-12

AI 速览

一句话:提出 DRMiner,从 Jira 问题日志中抽取设计备选方案及其论证,以缓解设计理由文档缺失问题。

软件架构通常需要权衡多种质量属性并支持长期维护,但开发者在缺乏即时收益时往往不愿记录设计理由(即设计备选方案以及支持或拒绝决策的论证),导致设计文档缺失,并在人员更替后引发架构侵蚀。已有研究尝试从开源社区提取设计知识,却因在线讨论语义复杂且缺少设计理由抽取基准,未能同时抽取解决方案及其对应论证。本文提出 DRMiner,面向 Jira 问题日志提取潜在设计理由;摘要未给出具体技术实现与实验评估结果。

问题
开发者在缺乏即时收益时不愿记录设计理由(设计备选方案及决策论证),导致设计文档缺失,并在人员更替后引发架构侵蚀;已有研究因在线讨论语义复杂且缺乏基准,难以同时抽取解决方案及其论证。
方法
提出 DRMiner,面向 Jira 问题日志提取潜在设计理由;但摘要未详述其具体抽取技术。
评估
摘要未给出评估方式与结果,亦未说明所用基准或指标。
原文摘要(Abstract)

Software architectures are usually meticulously designed to address multiple quality concerns and support long-term maintenance. However, there may be a lack of motivation for developers to document design rationales (i.e., the design alternatives and the underlying arguments for making or rejecting decisions) when they will not gain immediate benefit, resulting in a lack of standard capture of these rationales. With the turnover of developers, the architecture inevitably becomes eroded. This issue has motivated a number of studies to extract design knowledge from open-source communities in recent years. Unfortunately, none of the existing research has successfully extracted solutions alone with their corresponding arguments due to challenges such as the intricate semantics of online discussions and the lack of benchmarks for design rationale extraction.

链接与引用

DOI 原文 ·

BibTeX
@inproceedings{paperbot8338,
  title = {DRMiner: Extracting Latent Design Rationale from Jira Issue Logs},
  author = {Jiuang Zhao and Zitian Yang and Li Zhang and Xiaoli Lian and Donghao Yang and Xin Tan},
  booktitle = {ASE},
  year = {2024},
  doi = {10.1145/3691620.3695019}
}