Question

You are working as an intern at a new company. Your boss, Paul, was recently hired as a systems analyst and he needs to set up a structured walk-through/peer group review but isn’t quite clear on exactly what that involves. Since this is his first walk-through/peer group review, he wants to make a good impression. Paul has tasked you with finding the answers to the following questions:

1. What is the purpose of the structured walk-through/peer group review?
   1. Why does it need to be done? Is it something that historically has been proven to be beneficial?
2. How does the walk-through fit in with the SDLC?
   1. At what phase does this come into play?
   2. Does it impact whether or not they can move onto the next phase of the SDLC?
3. Who will Paul need to have involved?
   1. What roles will each team member play?
   2. What activities will each member be responsible for?
4. What deliverable(s) does the walk-through produce?

Answer 1

What is the purpose of the structured walk-through/peer group review? A Structured walkthrough can be regarded as static testing technique that performed in an organized way between a team or group of peers, those further can review and discuss the technical aspects of software development process, the main objective in this process is to find defects, so quality of the product can be Improved, Structured walkthroughs are basically used to detect the errors or defect associated in the system or process, however this can’t be used for correcting the errors, so structure Walkthroughs can’t be used for creating solutions of the issues found or for the discussion that is technical oriented, again walkthrough is finished, the responsible person can come for fixing the issues,

Why does it need to be done? Is it something that historically has been proven to be beneficial? Following are the points can be explained that the benefits drawn by structured walk through and those are having historical Importance, proven to be beneficial, It can save time and cost as defects are found earlier and rectified very early in the lifecycle, This can provide value added result from reviewers with different experience and technical backgrounds Further progress of the development process can be notified with the help of structured walk through and project management team become aware on the same Further participants get professional growth, as it create different development and maintenance methodologies,

How does the walk-through fit in with the SDLC? As SDLC or Software development Life Cycle is a process basically used by the software industry, by this, Quality software can be tested, designed and developed, so it can aims to produce high quality software and such software will meet the expectations of the customers, Reaches completion time and cost estimates with the Use of SDLC, again Structured Walk through will detect any defects and error during software development life cycle and each phases of the software development life cycle, also the task associated with software development life cycle needs to be properly performed and error free, thus, in such situation this walk through has to be performed, for this process, it will include author, presenter, Moderator, Reviewer and scribe for making the process outcome oriented,

At what phase does this come into play? Following are the phases associated with SDLC, those basically include Planning, Defining, Designing, Building, Testing, Deployment, whenever we talk about Structure walkthrough program, it becomes part of Testing, again Testing to be done in all the phases of Software development life cycle,

Does it impact whether or not they can move onto the next phase of the SDLC? All the phases activity to be checked as structure walkthrough works on detecting the Error, so each phases take its own importance, again any phases once detected with the error with the help of Structured walkthrough, so sufficient response strategy to be implemented, as a result next onwards stages of the SDLC will not be impacted,

Who will Paul need to have involved? Paul can act as a moderator in this process, as he will facilitate the walkthrough session and ensures the walkthrough agenda is followed and encourage all the reviewers to participate in the process,

What roles will each team member play? Team members can be regarded as presenter, as it develops the agenda for the walkthrough and presents the output being followed, Team members also can act as reviewers, thus can evaluate document under the test to evaluate whether is it accurate or not,

What activities will each member be responsible for? The Presenter will develop agenda for the Structure walkthrough and presents the Result or output being reviewed, Author will produce the document that under review, Moderator will facilitate the walkthrough session and ensure that whether such walkthrough agenda is being followed and encourages all the reviewers to participate in the process Reviewers will evaluate the document under test and determine whether the document is technically correct or not Scribe will do recording of entire structured walkthrough outcomes, further record the issue identified, technical comments, suggestions and the questions, those are not resolved,

What deliverable(s) does the walk-through produce? Following are the deliverables the structured Walk-through can produce, those are like, It can make the defect found and rectified very early in the lifecycle, so both time and cost get saved reasonably Create value added outcomes from the reviewers, those reviewers can be from different technical backgrounds and experience It can aware and make project management team on the same pages about the progress of development process Further the deliverables associated with creating maintenance methodologies, thus provide professional growth to the participants