Validating and prioritizing quality rules for managing technical debt: An industrial case study

D. Falessi, A. Voegele
{"title":"Validating and prioritizing quality rules for managing technical debt: An industrial case study","authors":"D. Falessi, A. Voegele","doi":"10.1109/MTD.2015.7332623","DOIUrl":null,"url":null,"abstract":"One major problem in using static analyzers to manage, monitor, control, and reason about technical debt is that industrial projects have a huge amount of technical debt which reflects hundreds of quality rule violations (e.g., high complex module or low comment density). Moreover the negative impact of violating quality rules (i.e., technical debt interest) may vary across rules or even across contexts. Thus, without a context-specific validation and prioritization of quality rules, developers cannot effectively manage technical debt. This paper reports on a case study aimed at exploring the interest associated with violating quality rules; i.e., we investigate if and which quality rules are important for software developers. Our empirical method consists of a survey and a quantitative analysis of the historical data of a CMMI Level 5 software company. The main result of the quantitative analysis is that classes violating several quality rules are five times more defect prone than classes not violating any rule. The main result of the survey is that some rules are perceived by developers as more important than others; however, there is no false positive (i.e., incorrect rule or null interest). These results pave the way to a better practical use of quality rules to manage technical debt and describe new research directions for building a scientific foundation to the technical debt metaphor.","PeriodicalId":396514,"journal":{"name":"2015 IEEE 7th International Workshop on Managing Technical Debt (MTD)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-11-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"18","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 IEEE 7th International Workshop on Managing Technical Debt (MTD)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MTD.2015.7332623","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 18

Abstract

One major problem in using static analyzers to manage, monitor, control, and reason about technical debt is that industrial projects have a huge amount of technical debt which reflects hundreds of quality rule violations (e.g., high complex module or low comment density). Moreover the negative impact of violating quality rules (i.e., technical debt interest) may vary across rules or even across contexts. Thus, without a context-specific validation and prioritization of quality rules, developers cannot effectively manage technical debt. This paper reports on a case study aimed at exploring the interest associated with violating quality rules; i.e., we investigate if and which quality rules are important for software developers. Our empirical method consists of a survey and a quantitative analysis of the historical data of a CMMI Level 5 software company. The main result of the quantitative analysis is that classes violating several quality rules are five times more defect prone than classes not violating any rule. The main result of the survey is that some rules are perceived by developers as more important than others; however, there is no false positive (i.e., incorrect rule or null interest). These results pave the way to a better practical use of quality rules to manage technical debt and describe new research directions for building a scientific foundation to the technical debt metaphor.
对管理技术债务的质量规则进行验证和排序:一个工业案例研究
使用静态分析器来管理、监视、控制和分析技术债务的一个主要问题是,工业项目有大量的技术债务,这反映了数百条质量规则的违反(例如,高复杂模块或低注释密度)。此外,违反质量规则(例如,技术债务利息)的负面影响可能因规则甚至上下文而异。因此,如果没有上下文特定的验证和质量规则的优先级,开发人员就不能有效地管理技术债务。本文报告了一个案例研究,旨在探讨违反质量规则的相关利益;也就是说,我们调查哪些质量规则对软件开发人员来说是重要的。我们的实证方法包括对一家CMMI五级软件公司的历史数据进行调查和定量分析。定量分析的主要结果是,违反几条质量规则的类比不违反任何规则的类的缺陷发生率高5倍。调查的主要结果是,开发者认为某些规则比其他规则更重要;然而,没有假阳性(即,不正确的规则或零利益)。这些结果为更好地实际使用质量规则来管理技术债务铺平了道路,并为构建技术债务隐喻的科学基础描述了新的研究方向。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信
小红书