Peer Review

Learning Objectives

• Define fault, error, and failure
• Illustrate how reviews alter effort across the software development life cycle
• Contrast “lightweight” peer review with formal reviews
• Critique source code to improve the implementation of a software system

How to Complete this Lesson

Complete the following learning activities: (2.5 hours total)

1. Read “Clean Code Isn’t Enough: It Must Be Crystal Clear, Too” (5 minutes)
2. Watch the following videos about peer review: (30 minutes total)
   • Peer Review Overview and Anti-Patterns (2 minutes)
   • Most Effective Software Quality Practices (2 minutes)
   • Peer Reviews Are Effective and Efficient (3 minutes)
   • Fagan Style Inspections: The Gold Standard (4 minutes)
   • Rules for Successful Peer Reviews (4 minutes)
   • Perspective-Based Peer Reviews (2 minutes)
   • Peer Review Checklist Template (template) (4 minutes)
   • Peer Review Case Study - Course Project (5 minutes)
   • Review Everything in the Vee – not just code (1 minute)
   • Peer Review Economics (3 minutes)
3. Read “Don’t waste time on Code Reviews” (15 minutes)
4. Watch Code Review on GitHub (2 minutes)
5. Review for Graded Review I (30 minutes)
6. Participate in the synchronous session during the class meeting time (optional)
7. Complete the quiz (5–8 minutes)
8. Work on the specification (60 minutes)
   • Review the sections written by others, ensuring that the specification as a whole is unambiguous

Due

As a reminder, the following is due this lesson:

• Quiz: Peer Review

Resources

Videos

---

Use Cases Graded Review I