Walkthroughs
- 1. Mrs. R. Nancy Beaulah, MCA., M.Phil., Assistant Professor, Department of Computer Applications (UG), V.V.Vanniaperumal College for Women (Autonomous), Virudhunagar.
- 2. Walkthroughs Walkthrough team contains a Reviewee and a three to five reviewers. Walkthrough will be best if there is only one or two reviewers. It will be then like discussion with a colleague. Members of a Walkthrough Project Leader Other members from the project team Quality assurance group representative Technical writer & technical personnel who have interest in the project
- 3. Walkthroughs Customers and users may be included during the analysis and design phase Should be excluded during the following sessions. High level managers should not attend the walkthrough Should be conducted in an open non-defensive atmosphere. Vice president or department manager may inhibit the review process.
- 4. Walkthroughs Goal of walkthroughs are to discover the problem areas. Problems cannot be resolved during walkthroughs. The Reviewee has to solve the problem after the walkthrough. The Reviewee may get help from one or two reviewers. But the responsibility is for the Reviewee. A follow up meeting can be conducted to check the work status.
- 5. Walkthroughs Guidelines to make walkthrough beneficial 1. Everyone’s work should be reviewed in a periodical manner. 2. This will provide a vehicle of communication among team members 3. Project leader’s technical work should also be reviewed. 4. Project leader should provide a healthy non- defensive environment for the Reviewees.
- 6. Walkthroughs 5. Walkthroughs are for detecting errors only and not to correct the errors. 6. Reviewee should note the errors and rectify in the following sessions. 7. One of the member should be designated as recording secretary. 8. Major issues alone should be discussed. Minor issues should be avoided. 9. Major issue of coding efficiency may be discussed. Minor issue of coding style should be avoided.
- 7. Walkthroughs 10. One moderator should be assigned in order to keep the walkthrough in a positive atmosphere and to focus on Major issues. 11. Walkthrough session should end in 2 hours. 12. This leads to discuss only major issues and make the session more focused. 13. It also leads to active participation of reviewers.
- 8. Walkthroughs Success of walkthrough depends on establishing positive and non-threatening environment. Project leader, senior programmer and walkthrough moderator should be trained for conducting walkthroughs. They should also trained for Group Dynamics to ensure correct psychological setting. Sufficient time should be allotted to the walkthrough. It should be consider as a part of work rather than over commitment.
- 9. Walkthroughs Benefits of Walkthroughs Errors are identified at earlier stage Easy and least expensive to fix the errors. Team communication is improved Personnel learn new techniques from one another. Work products can be reviewed as public documents. Team members get great job satisfaction.
- 10. Walkthroughs - Summary Walkthroughs should not be used for evaluating employees. Project leader can able to know the strength and weakness of individual team members. Project works are assigned according to the team member’s ability. Team members can able to learn from their colleagues and able to overcome their initial weaknesses. In some cases, reassignment of work and dismissal of unsuitable employee is also necessary But this should be done after a period of time.
- 11. References Software Engineering Concepts, Richard Fairley, Tata McGraw Hill Edition.