Code Inspection Activity

The team is to select two classes to inspect. The classes chosen must have significant state (data) and behavior (functionality); simple data holders with only getter and setter methods are not acceptable. To give you the greatest opportunity to learn from this activity, no team member can assume the same inspection role twice, and every team member must assume one of the three primary roles (moderator, reader, scribe) at least once. In no event shall the component's author also act as moderator or reader.

The following conditions must be met prior to any team entering a meeting room to begin its inspection:

All members of the team are present at the start of class on the day of the inspection.

Each team must hand in initial copies of the code inspection report for each of the classes to be inspected with the following information filled in:

• The team account and project name.
• The name of the component being inspected (e.g., SomeFile.java).
• The date of the inspection.
• The (primary) author of the component.
• The team member who will act as moderator.
• The team member who will be reader.
• The team member who will be scribe.
• The names of other team members who are simply inspectors for this component.

Each team member must bring to the inspection two identical annotated (marked up) copies of each of the components being inspected, showing the pre-inspection effort the member expended in finding potential flaws. One of the copies will be given to the instructor; the other will be used by the team member as a reference during the inspection.

The instructor may deny any team or any team member the right to participate in an inspection if the above conditions are not met. Assuming the conditions are met, the team will proceed to perform the inspection, with occasional observation by the instructor (who, of course, has to observe all teams).