Framework for Software Code Reviews and Inspections in a Classroom Environment

Abstract

Code reviews and inspections have the purpose to ensure that the code has sufficient quality to be released. It is generally seen as an economical way of finding errors, increase team productivity and sharing technical and product knowledge among team members. This approach is traditionally adopted in software development companies, but their practices may be useful in other contexts, such as in the process of learning software engineering. In this sense, this study proposes an innovative framework for conducting code reviews in a Computer Science course. The proposed framework can be applied in any object-oriented program language, and it is sufficiently concise to be applied in the classroom, namely in a 90-minute session in which all students are invited to collaborate in this process. The findings suggest that code reviews in an academic context can help students to strategically reflect about the performed work, enhance their soft skills, and increase their ability to work in groups. On the other hand, as the main challenges, the findings reveal that students typically don't have previous experience in performing inspections and it can become difficult to perform a complete inspection in a classroom session.

Application of Constructive Modeling and Process Mining Approaches to the Study of Source Code Development in Software Engineering Courses

“…Only a few studies have reported about using code review in computer science courses [1,22,23]. However, the findings suggest that using code reviews by students increases their self-confidence and that the benefits gained in the classroom are similar to the benefits found in production.…”

“…Digital Object Identifier (DOI): 10.24138/jcomss-2021-0046 quality of corresponding developing process. One of the most examined methods of refining a program quality is using code review [1]. A modern code review, frequently used in practice these days, is informal, tool-based, and asynchronous [2].…”