Adopting Code Reviews for Agile Software Development

Bernhart, Mario; Mauczka, Andreas; Grechenig, Thomas

doi:10.1109/agile.2010.18

Cited by 18 publications

(9 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…MCR is often supported by tools, preferably integrated into the development environment (IDE) [12]. Bernhart et al introduced one such tool for the Eclipse IDE, ReviewClipse [9], now Mylyn Reviews [39]. ReviewClipse automatically creates a new 'review process,' assigns a fitting reviewer, and opens a compare viewer for this commit.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Modern code reviews in open-source projects: which problems do they fix?

Beller

Bacchelli

Zaidman

et al. 2014

Proceedings of the 11th Working Conference on Mining Software Repositories

201

140

View full text Add to dashboard Cite

Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7-35% of review comments are discarded and that 10-22% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.

show abstract

Section: Related Workmentioning

confidence: 99%

“…Consequently, researchers and practitioners developed more lightweight, ad hoc code reviewing processes to better suit environments with test-driven and iterative development [6,9,34,37,47]. Modern Code Review.…”

Section: Related Workmentioning

confidence: 99%

Modern code reviews in open-source projects: which problems do they fix?

Beller

Bacchelli

Zaidman

et al. 2014

Proceedings of the 11th Working Conference on Mining Software Repositories

201

140

View full text Add to dashboard Cite

show abstract

“…Code review is a way to reduce the risk of error and improve the quality of software by checking the source code to identify defects or bugs that may occur during software development. Moreover, such a review can standardize the source code [11]. When organizations or projects that require software development use this code review process, it ensures that the developed code will meet the specifications or needs of the user and that the impacts of source code modifications are minimized.…”

Section: A Peer Code Review For Oss Projectsmentioning

confidence: 99%

The Impact of Peer Code Review on Software Maintainability in Open-Source Software: A Case Study

Nanthaamornphong¹,

Kitpanich²

2022

IJACSA

View full text Add to dashboard Cite

Recently, open-source software (OSS) has become a considerably popular and reliable source of functionality corrections. OSS also allows software developers to reduce technical debt in software development. However, previous studies have shown that the main problem within OSS development is the lack of systematic processes and formal documents related to system development, such as requirements, designs, and testing. This feature of OSS development causes problems in the software quality, such as those related to security and maintainability. In this research, the authors focused on the software's maintainability because this attribute has to greatest potential to reduce the cost and increase the productivity of the software development process. There is currently no existing research that examines whether OSS developers pay attention to software maintainability. To better understand how OSS developers improve software maintainability, this research aims to answer the question: "Are developers interested in software maintainability under the modern code review of open-source software projects?" To answer the research question, the authors investigated the code review process in which the OSS developers changed the code based on a review of code comments related to maintenance and collected the sub-characteristics associated with software maintainability from the existing literature. The authors examined the review comments from two OSS projects: Eclipse and Qt. The results suggest that the number of code revisions due to maintenance issues was moderate and that the OSS developers tend to improve source code quality. This direction could be observed from the increasing number of modifications on given maintenance-based comments over the years. Therefore, an implication of this is the possibility that OSS project developers are interested in software maintainability.

show abstract

“…For code inspection the following tools were identified by the authors through a systematic literature mapping: Team Tracks (DeLine et al, 2005), ReviewClipse -RC (Bernhart et al, 2010), SCRUB (Holzmann, 2009), ICICLE (Brothers et al, 1990), Codestriker and ReviewPro (Remillard, 2005).…”

Section: The Crista Toolmentioning

confidence: 99%

Code Inspection Supported by Stepwise Abstraction and Visualization - An Experimental Study

Belgamo

Hernandes

Zamboni

et al. 2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Background: In order to inspect source code effectively and efficiently, in a previous work the use of visualization for supporting the reading technique Stepwise Abstraction was proposed and implemented in the CRISTA tool. Visualization aids code comprehension, which is an essential task for a successful inspection. Goal: The objective of this paper is to evaluate the effectiveness and efficiency of using stepwise abstraction supported by visualization for defects detection, in comparison to an ad-hoc approach. Method: A controlled experiment was conducted with two groups of undergraduate students. One group inspected the Java source code of the Paint software using the approach implemented in CRISTA and the other group inspected the code using an ad-hoc approach. Results: The general performance of the subjects who used Stepwise Abstraction supported by visualization was better than that of the subjects who used the ad-hoc approach. Besides, the subjects' experience in inspection and Java did not influence the identification of defects. Conclusion: the results reveal that the use of Stepwise Abstraction and visualization promotes better performance in detecting defects than the ad-hoc approach. In future work, other approaches are being investigated as well as the support of the approaches for different types of defects.

show abstract

Adopting Code Reviews for Agile Software Development

Cited by 18 publications

References 20 publications

Modern code reviews in open-source projects: which problems do they fix?

Modern code reviews in open-source projects: which problems do they fix?

The Impact of Peer Code Review on Software Maintainability in Open-Source Software: A Case Study

Code Inspection Supported by Stepwise Abstraction and Visualization - An Experimental Study

Contact Info

Product

Resources

About