CpSc372

Introduction to Software Engineering

Assignment 6

Reviews and Inspections

Goal: Gain experience in conducting reviews and inspections

Description: During the design process, before the code is available for execution, design inspections provide a means to examine the design in depth. The inspection process is labor intensive. Designers must examine the design in detail. This examination is guided by a set of scenarios that come from the use cases.

Procedure:

1. Form a team for this assignment by joining two of the existing teams together. Then arrange with ANOTHER group (not one of the two) to use their model from assignment 5 as the target of the evaluation.
2. Agree on the meaning of correct, consistent and complete for your team.
3. Take a scenario from one of the use cases. (Use a main scenario, an alternative scenario, and one exceptional scenario.)
4. Use the scenario to construct a sequence diagram that contains objects from the classes in the class diagrams.
5. Identify errors in the class definitions, state diagrams, etc.
6. Write an evaluation of the design. Organize the evaluation around the three criteria: correct, consistent and complete. Give a copy to the team that constructed the design and handin one copy.

Turn-in: The scenarios, the sequence diagrams, and the written evaluation.

Due: 4 pm Monday Oct 16 in the dept office

Points 2 points

Team: 4 person team assignment

Evaluation: The scenarios will be evaluated as to their coverage of the system. The sequence diagrams will be evaluated on completeness. The evaluation will be graded on the quality of the advice and on the writing.