Powered by
2013 21st International Conference on Program Comprehension (ICPC),
May 20–21, 2013,
San Francisco, CA, USA
Industry Track
Mon, May 20, 16:30 - 17:30, Bayview B
On the Understanding of Programs with Continuous Code Reviews
Mario Bernhart and Thomas Grechenig
(TU Vienna, Austria)
Code reviews are a very effective, but effortful quality assurance technique. A major problem is to read and understand source-code that was produced by someone else. With different programming styles and complex interactions, understanding the code under review is the most expensive sub- task of a code review. As with many other modern software engineering practices, code reviews may be applied as a continuous process to reduce the effort and support the concept of collective ownership. This study evaluates the effect of a continuous code review process on the understandability and collective ownership of the code base. A group of 8 subjects performed a total of 114 code reviews within 18 months in an industrial context and conducted an expert evaluation according to this research question. This study concludes that there is a clear positive effect on the understandability and collective ownership of the code base with continuous code reviews, but also limiting factors and drawbacks for complex review tasks.
@InProceedings{ICPC13p192,
author = {Mario Bernhart and Thomas Grechenig},
title = {On the Understanding of Programs with Continuous Code Reviews},
booktitle = {Proc.\ ICPC},
publisher = {IEEE},
pages = {192--198},
doi = {},
year = {2013},
}
Applying Clone Change Notification System into an Industrial Development Process
Yuki Yamanaka, Eunjong Choi, Norihiro Yoshida,
Katsuro Inoue, and Tateki Sano
(Osaka University, Japan; Nara Institute of Science and Technology, Japan; NEC, Japan)
Programmers tend to write code clones unintentionally even in the case that they can easily avoid them. Clone change management is one of crucial issues in open source software (OSS) development as well as in industrial software development (e.g., development of social infrastructure, financial system, and medical equipment). When an industrial developer fixes a defect, he/she has to find the code clones corresponding to the code fragment including it. So far, several studies performed on the analysis of clone evolution in OSS. However, to our knowledge, a few researches have been reported on an application of a clone change notification system to industrial development process. In this paper, we introduce a system for notifying creation and change of code clones, and then report on the experience with 40-days application of it into a development process in NEC Corporation. In the industrial application, a developer successfully identified ten unintentionally-developed clones that should be refactored.
@InProceedings{ICPC13p199,
author = {Yuki Yamanaka and Eunjong Choi and Norihiro Yoshida and Katsuro Inoue and Tateki Sano},
title = {Applying Clone Change Notification System into an Industrial Development Process},
booktitle = {Proc.\ ICPC},
publisher = {IEEE},
pages = {199--206},
doi = {},
year = {2013},
}
proc time: 0.23