Do code review practices impact design quality? A case study of the Qt, VTK, and ITK projects

2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER) Pub Date : 2015-03-02 DOI:10.1109/SANER.2015.7081827

Rodrigo Morales, Shane McIntosh, Foutse Khomh

{"title":"Do code review practices impact design quality? A case study of the Qt, VTK, and ITK projects","authors":"Rodrigo Morales, Shane McIntosh, Foutse Khomh","doi":"10.1109/SANER.2015.7081827","DOIUrl":null,"url":null,"abstract":"Code review is the process of having other team members examine changes to a software system in order to evaluate its technical content and quality. A lightweight variant of this practice, often referred to as Modern Code Review (MCR), is widely adopted by software organizations today. Previous studies have established a relation between the practice of code review and the occurrence of post-release bugs. While the prior work studies the impact of code review practices on software release quality, it is still unclear what impact code review practices have on software design quality. Therefore, using the occurrence of 7 different types of anti-patterns (i.e., poor solutions to design and implementation problems) as a proxy for software design quality, we set out to investigate the relationship between code review practices and software design quality. Through a case study of the Qt, VTK and ITK open source projects, we find that software components with low review coverage or low review participation are often more prone to the occurrence of anti-patterns than those components with more active code review practices.","PeriodicalId":355949,"journal":{"name":"2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2015-03-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"113","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SANER.2015.7081827","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 113

Abstract

Code review is the process of having other team members examine changes to a software system in order to evaluate its technical content and quality. A lightweight variant of this practice, often referred to as Modern Code Review (MCR), is widely adopted by software organizations today. Previous studies have established a relation between the practice of code review and the occurrence of post-release bugs. While the prior work studies the impact of code review practices on software release quality, it is still unclear what impact code review practices have on software design quality. Therefore, using the occurrence of 7 different types of anti-patterns (i.e., poor solutions to design and implementation problems) as a proxy for software design quality, we set out to investigate the relationship between code review practices and software design quality. Through a case study of the Qt, VTK and ITK open source projects, we find that software components with low review coverage or low review participation are often more prone to the occurrence of anti-patterns than those components with more active code review practices.

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

代码审查实践会影响设计质量吗?Qt、VTK和ITK项目的案例研究

代码审查是让其他团队成员检查对软件系统的更改，以评估其技术内容和质量的过程。这种实践的一个轻量级变体，通常被称为现代代码审查(Modern Code Review, MCR)，今天被软件组织广泛采用。以前的研究已经建立了代码审查实践与发布后bug发生之间的关系。虽然先前的工作研究了代码审查实践对软件发布质量的影响，但代码审查实践对软件设计质量的影响仍然不清楚。因此，使用7种不同类型的反模式(例如，设计和实现问题的糟糕解决方案)作为软件设计质量的代理，我们开始调查代码审查实践和软件设计质量之间的关系。通过对Qt、VTK和ITK开源项目的案例研究，我们发现具有低审查覆盖率或低审查参与度的软件组件通常比那些具有更活跃的代码审查实践的组件更容易出现反模式。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文去求助

来源期刊

2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER)

自引率

0.00%

发文量