Jul 2026· Annual Conference on Innovation and Technology in Computer Science Education· 0 citations· 19 references
Computer Science
TL;DR
This experience report describes how peer code reviews were implemented in an upper-division software engineering course that focuses on making modifications to large, existing code bases (i.e., brownfield development).
Abstract
Peer code reviews involve students conducting a code review of a classmate's submission to a programming assignment. While peer code reviews have an established history of being used and studied in computing education, they have primarily been documented in introductory computing courses. This experience report describes how we implemented peer code reviews in an upper-division software engineering course that focuses on making modifications to large, existing code bases (i.e., brownfield development). We discuss the perceived learning benefits, perceived challenges, and agreement between peer and course staff reviews. Overall, students enjoyed being able to see different approaches to the programming task they had just submitted, but expressed concerns about feeling qualified to make effective peer code reviews due to their limited software engineering experience and the difficulty of assessing code design. We also find that students are capable of evaluating the functional correctness of their peer's submission, but struggle to give accurate assessments of their peer's design and code style. We conclude with recommendations specifically for instructors who wish to use peer code reviews in upper-division software engineering courses, such as using a structured template to scaffold the peer code reviews and allowing multiple opportunities to provide code reviews to improve students' self-efficacy.
EvOwl includes novel features that are designed with large-scale and long-term projects in mind, such as support for using code coverage to focus students' attention on specific features within a large code base and a metric-guided approach to help students compare software quality across different implementations.
Adam Tillou, Praise O. Mayor, S. Rixner et al.· Annual Conference on Innovat...· 0 citations
Qu quantitative analysis of 622 peer reviews on review time, length, and correctness reveals that students are better at assessing actual correct submissions as correct than incorrect ones as incorrect, with test results and checklists slightly increasing their performance in identifying incorrect submissions.
Findings are interpreted as evidence that course-aware style feedback is promising as a pre-submission revision aid, but that future versions should combine deterministic rule checks with LLM-generated explanations, rule citations, and stronger verification support.
Ethan Dickey, L. Vento, Peter Kurto et al.· 0 citations
It is suggested that undesirable tasks are an integral part of students’ academic software development experience and have meaningful emotional and motivational consequences, and that these insights offer opportunities for educators to design curricula and learning environments that better address human dispositions, m...
Comparisons show that measured signal depends on production context and that process patterns can complement weak final-code signal in educational repositories, and that such models are appropriate only as instructor-mediated decision support, not as independent proof of authorship.
The results show that RSEs most often improved code review by using pull requests, defining review expectations, adding lightweight process steps, and using tools and automation to reduce effort and increase consistency.
Md. Ariful Islam Malik, Jeffrey C. Carver, Nasir U. Eisty· Practice and Experience in A...· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.