Code Red: The Business Impact of Code Quality - A Quantitative Study of 39 Proprietary Production Codebases

Adam Tornhill, Markus Borg
{"title":"Code Red: The Business Impact of Code Quality - A Quantitative Study of 39 Proprietary Production Codebases","authors":"Adam Tornhill, Markus Borg","doi":"10.1145/3524843.3528091","DOIUrl":null,"url":null,"abstract":"Code quality remains an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for time-to-market and new features. The resulting technical debt is estimated to waste up to 42% of developers' time. At the same time, there is a global shortage of software developers, meaning that developer productivity is key to software businesses. Our overall mission is to make code quality a business concern, not just a technical aspect. Our first goal is to understand how code quality impacts 1) the number of reported defects, 2) the time to resolve issues, and 3) the predictability of resolving issues on time. We analyze 39 proprietary production codebases from a variety of domains using the CodeScene tool based on a combination of source code analysis, version-control mining, and issue information from Jira. By analyzing activity in 30,737 files, we find that low quality code contains 15 times more defects than high quality code. Furthermore, resolving issues in low quality code takes on average 124% more time in development. Finally, we report that issue reso-lutions in low quality code involve higher uncertainty manifested as 9 times longer maximum cycle times. This study provides evi-dence that code quality cannot be dismissed as a technical concern. With 15 times fewer defects, twice the development speed, and substantially more predictable issue resolution times, the business advantage of high quality code should be unmistakably clear.","PeriodicalId":149335,"journal":{"name":"2022 IEEE/ACM International Conference on Technical Debt (TechDebt)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2022-03-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"5","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2022 IEEE/ACM International Conference on Technical Debt (TechDebt)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3524843.3528091","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 5

Abstract

Code quality remains an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for time-to-market and new features. The resulting technical debt is estimated to waste up to 42% of developers' time. At the same time, there is a global shortage of software developers, meaning that developer productivity is key to software businesses. Our overall mission is to make code quality a business concern, not just a technical aspect. Our first goal is to understand how code quality impacts 1) the number of reported defects, 2) the time to resolve issues, and 3) the predictability of resolving issues on time. We analyze 39 proprietary production codebases from a variety of domains using the CodeScene tool based on a combination of source code analysis, version-control mining, and issue information from Jira. By analyzing activity in 30,737 files, we find that low quality code contains 15 times more defects than high quality code. Furthermore, resolving issues in low quality code takes on average 124% more time in development. Finally, we report that issue reso-lutions in low quality code involve higher uncertainty manifested as 9 times longer maximum cycle times. This study provides evi-dence that code quality cannot be dismissed as a technical concern. With 15 times fewer defects, twice the development speed, and substantially more predictable issue resolution times, the business advantage of high quality code should be unmistakably clear.
红色代码:代码质量的商业影响——对39个专有生产代码库的定量研究
代码质量仍然是一个抽象的概念,无法在业务层面上获得牵引力。因此,软件公司一直在用代码质量换取上市时间和新特性。由此产生的技术债务估计浪费了开发人员42%的时间。与此同时,全球软件开发人员短缺,这意味着开发人员的生产力是软件业务的关键。我们的总体任务是使代码质量成为业务问题,而不仅仅是技术问题。我们的第一个目标是了解代码质量如何影响1)报告缺陷的数量,2)解决问题的时间,以及3)按时解决问题的可预测性。基于源代码分析、版本控制挖掘和来自Jira的问题信息的组合,我们使用codescent工具分析了来自不同领域的39个专有产品代码库。通过分析30,737个文件中的活动,我们发现低质量代码包含的缺陷是高质量代码的15倍。此外,解决低质量代码中的问题平均要多花124%的开发时间。最后,我们报告说,低质量代码中的问题解决涉及更高的不确定性,表现为最长周期时间的9倍。这项研究提供的证据表明,代码质量不能作为一个技术问题而被忽视。由于缺陷减少了15倍,开发速度提高了一倍,问题解决时间大大提高了,高质量代码的业务优势应该是显而易见的。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约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学术官方微信