首页> 外文会议>Software analysis, testing, and evolution >Which Defect Should Be Fixed First? Semantic Prioritization of Static Analysis Report
【24h】

Which Defect Should Be Fixed First? Semantic Prioritization of Static Analysis Report

机译:首先应修复哪些缺陷?静态分析报告的语义优先级

获取原文
获取原文并翻译 | 示例

摘要

The usability of static analyzers is plagued by excessive false alarms. It is laborious yet error-prone to manually examine the spurious-ness of defect reports. Moreover, the inability to preclude overwhelming false alarms deters user's confidence on such tools and severely limits their adoption in development cycles. In this paper, we propose a semantic approach for prioritizing defect reports emitted by static analysis. Our approach evaluates the importance of defect reports by their fatality and priorities defects by their affection to critical functions. Compared to the existing approaches that prioritize defect reports by analyzing external attributes, ours substantially utilizes semantic information derived by static analysis to measure the severity of defect reports more precisely. We have implemented a prototype which is evaluated to real-world code bases, and the results show that our approach can effectively evaluate the severity of defects.
机译:过多的错误警报困扰着静态分析仪的可用性。手动检查缺陷报告的虚假性既费力又容易出错。此外,无法排除压倒性的错误警报会阻止用户对此类工具的信心,并严重限制了它们在开发周期中的采用。在本文中,我们提出了一种语义方法,用于对静态分析发出的缺陷报告进行优先级排序。我们的方法通过缺陷报告的致命性和缺陷优先级对关键功能的影响来评估缺陷报告的重要性。与通过分析外部属性对缺陷报告进行优先级排序的现有方法相比,我们的方法充分利用了通过静态分析得出的语义信息来更精确地测量缺陷报告的严重性。我们已经实现了一个对真实代码库进行评估的原型,结果表明我们的方法可以有效地评估缺陷的严重性。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号