检索规则说明:AND代表“并且”;OR代表“或者”;NOT代表“不包含”;(注意必须大写,运算符两边需空一格)
检 索 范 例 :范例一: (K=图书馆学 OR K=情报学) AND A=范并思 范例二:J=计算机应用与软件 AND (U=C++ OR U=Basic) NOT M=Visual
作 者:刘文杰[1] 江贺[1] LIU Wenjie;JIANG He(School of Software,Dalian University of Technology,Dalian,Liaoning 116621,China)
机构地区:[1]大连理工大学软件学院
出 处:《计算机工程与应用》2019年第14期48-53,208,共7页Computer Engineering and Applications
基 金:国家自然科学基金(No.61175062)
摘 要:软件缺陷报告的严重性对缺陷的解决具有关键作用。随着软件规模的不断扩大,使用开源的软件缺陷跟踪系统成为海量缺陷信息数据的主要处理方法。分析缺陷报告严重性在数据仓库中的作用,是处理软件缺陷的重要内容。通过对Bugzilla缺陷跟踪系统数据的研究和分析,发现不同项目的属性特征差异较大,同时在修复率、解决时长、开发者、组件等属性上的统计特征具有一致性。对Mozilla项目和Eclipse项目的数据进行系统分析,并根据不同组件和项目中严重性程度分布情况,认为软件缺陷报告严重性程度的提升会导致缺陷修复率的提高,同时严重性程度为normal级别的缺陷解决时长最短,开发者持有缺陷的数量越高其修复率越低。The severity of software bug reporting is critical to the resolution of bugs. With the continuous expansion of software scale, using the open source software bug tracking system becomes the main processing method of mass bug information data. Analyzing the importance of bug reporting in data warehouse is an important part of dealing with software bug. In Bugzilla bug tracking system, the attribute features of different projects are quite different, and the statistical features are consistent in such attributes as repair rate, solution duration, developer, component, etc. The Mozilla project and Eclipse project data are systematically analyzed and distributed according to the severity of different components and projects. It is believed that the increase in the severity of software bug report will lead to the continuous increase in bug repair rate. Meanwhile, the bug with normal severity will be solved for the shortest time, and the higher the number of bugs, the lower the repair rate.
关 键 词:计算机应用技术 开源软件 缺陷报告 严重等级 解决方案 修复率
分 类 号:TP311.5[自动化与计算机技术—计算机软件与理论]
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在载入数据...
正在链接到云南高校图书馆文献保障联盟下载...
云南高校图书馆联盟文献共享服务平台 版权所有©
您的IP:216.73.216.145