The document discusses verification as the process of evaluating whether work products meet specified requirements, ensuring they are built according to design specifications. It details the walkthrough method for informal reviews, where participants, led by a designer or programmer, provide feedback on technical quality, identify errors, and suggest improvements. The advantages and disadvantages of walkthroughs are highlighted, including increased knowledge for the team and challenges with communication and stakeholder participation.

1. VERIFICATION AND
DESIGN
WALKTHROUGH
Presented By Robin (23188)

2. VERIFICATION
Verification is the process of evaluating work-
products of a development phase to determine whether
they meet the specified requirements.
Verification ensures that the product is built according
to the requirements and design specifications.
It also answers to the question , ” Are we building
the product right. ”

3. WALKTHROUGH
Method of conducting informal group/individual review is called
walkthrough.
 In walkthrough designer or programmer leads members of the
development team and other interested parties through a software
product.
 The participants ask questions & make comments about possible
errors; violation of development standards, or may suggest
improvement on the article.
 It can be pre-planned and can be conducted at need basis.
 Generally people working on the work product are involved in the
walkthrough process.

4. WALKTHROUGH
• A software walkthrough is done for several reasons.
• Here are some reasons:
 To gather feedback on technical quality of the document.
It helps identify and rectify errors in the early stages of SDLC.
• When is Software Walkthrough Needed?
 To review the source code.
It is valuable for reviewing Software Documentation.

5. WHERE IS A SOFTWARE
WALKTHROUGH DONE?
• Meeting Rooms.
• Virtual Meeting.
• In Testing Environment.
• Conference Rooms.
• Within the Development Environments.

6. STRUCTURED
WALKTHROUGH
PARTICIPANTS
• AUTHOR: The author of the document under review.
• PRESENTER: The presenter usually develops the agenda.
• MODERATOR: The moderator facilitates the walkthrough
session, ensures the walkthrough agenda is followed and
encourages all the reviewers to participate.
• REVIEWERS: The reviewers evaluate the document under test to
determine if it is technically accurate.

7. ADVANTAGES
• To explain and discuss the information in the document.
• To verify the validity of the system.
• Acts as a “proof of concept” at an early stage.
• Increases the knowledge of the entire team related to the code in
question.
•Incorporates multiple perspectives.

8. Disadvantages
• Team members from different cultural backgrounds may face
challenges expressing their opinions freely.
• In effective communication can hinder the success of a
walkthrough.
• Getting key stakeholders to participate in the walkthrough can
be difficult.
• It is not suitable for large projects as the size of the project may
make it more challenging to review thoroughly.

9. Thank You