Improving quality with software inspections
Software Development
Electronic peer review and peer grading in computer-science courses
Proceedings of the thirty-second SIGCSE technical symposium on Computer Science Education
Software Inspection
Automatic assignment management and peer evaluation
Journal of Computing Sciences in Colleges
Expertiza: students helping to write an OOD text
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Exploring studio-based instructional models for computing education
Proceedings of the 39th SIGCSE technical symposium on Computer science education
Integrating pedagogical code reviews into a CS 1 course: an empirical study
Proceedings of the 40th ACM technical symposium on Computer science education
Proceedings of the ACM 2009 international conference on Supporting group work
Online vs. face-to-face pedagogical code reviews: an empirical comparison
Proceedings of the 42nd ACM technical symposium on Computer science education
Tools for "contributing student learning"
ACM Inroads
Tools for "contributing student learning"
Proceedings of the 2010 ITiCSE working group reports
Transforming the CS classroom with studio-based learning
Proceedings of the 43rd ACM technical symposium on Computer Science Education
ACM Transactions on Computing Education (TOCE)
Talking about code: Integrating pedagogical code reviews into early computing courses
ACM Transactions on Computing Education (TOCE) - Special Issue on Alternatives to Lecture in the Computer Science Classroom
Teaching operating systems using code review
Proceedings of the 45th ACM technical symposium on Computer science education
Hi-index | 0.00 |
Inspired by the formal code inspection process commonly used in the software industry, we have been exploring the use of pedagogical code reviews (PCRs), in which a team of three to four students, led by a trained moderator, (a) walk through segments of each other's programming assignments, (b) check the code against a list of best coding practices, and (c) discuss and log issues that arise. We have found that PCRs not only improve the quality of students' code, but also positively impact students' communication and sense of community. However, implementing PCRs also presents a key logistical challenge: how to make code solutions and review results accessible to team members before, during, and after the team reviews? To address this challenge, we are developing an online environment specifically tailored to support PCRs. Our environment enables students to submit their code solutions; to review team members' code solutions on-line prior to PCRs; to carry out PCRs; and to resubmit their solutions based upon the results of the PCRs. In an empirical evaluation of the environment in a CS1 course, we found that it not only eased the logistics of implementing PCRs, but also improved the organization and efficiency of the PCR process.