A controlled experiment in program testing and code walkthroughs/inspections
Communications of the ACM
The effects of pair-programming on performance in an introductory programming course
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Strengthening the Case for Pair Programming
IEEE Software
The impact of pair programming on student performance, perception and persistence
Proceedings of the 25th International Conference on Software Engineering
Peer testing in Software Engineering Projects
ACE '04 Proceedings of the Sixth Australasian Conference on Computing Education - Volume 30
A design for team peer code review
Proceedings of the 36th SIGCSE technical symposium on Computer science education
Does personality matter?: an analysis of code-review ability
Communications of the ACM - ACM at sixty: a look back in time
Integrating pedagogical code reviews into a CS 1 course: an empirical study
Proceedings of the 40th ACM technical symposium on Computer science education
Peer review in CS2: conceptual learning
Proceedings of the 41st ACM technical symposium on Computer science education
| Hi-index | 0.05 |
It is well known that peer reviews are often effective in finding software bugs. This paper provides a code inspection exercise in which students work in teams to identify problems in code for a web crawler. The code is intentionally poorly written and the code used to work until the website that it visits changed its format! Students must identify poor design and documentation issues in the code. We gave this assignment to student teams in two separate semesters and found that all students identified design and documentation issues. Students were then given an assignment to either modify the existing code or to rewrite a new web crawler from scratch. Even though the modifications would have been relatively small, every team chose to rewrite the code from scratch and cited poor design and documentation issues for this decision. Our in-class discussion of the exercise revealed that the exercise illuminated the importance of good documentation.