Software Engineering

Guidelines for Structured Walkthrough

1)Designate a team member to initiate the walkthrough. Select the scenario that is chronologically earliest in your set of scenarios. (You do not have to walkthrough every scenario, just a representative subset)

2)As the team member reads or describes the activities of the scenario, another designated team member points out the interobject links on the collaboration diagram that facilitate this activity. The team members who are responsible for implementing each class involved in the collaboration should scrutinize the methods characterized in each link to ensure that the necessary parameter values are available to the class issuing the method invocation, and that the parameter values communicated to the class implementing class are sufficient to carry out the behavior being requested.

3)When everyone is happy with a particular collaboration, switch to a new scenario. Let a different team member read this scenario, and so on.

4)Make note of any unresolved issues that can't be easily solved. Address these issues later rather than holding up the progress of the walkthrough.

5)When you are done. Hand in your collaboration diagrams and your sequence diagram to the instructor.