Scribd Logo
Upload

Welcome to Scribd!

  • 45 views

    Walkthrough

    Uploaded by

    Aryaman Singh
    An informal review involves a developer distributing a work product to peers for feedback, while a formal review is conducted by a team leader or moderator to identify defects. There are different types of reviews, including desk checks where peers provide informal comments, walkthroughs where the author guides an informal discussion, and inspections where a moderator leads a formal meeting to identify and log defects. Formal inspections involve preparation, an overview, page-by-page review, rework, and follow up to approval. Code reviews specifically examine source code or patches to identify defects or improvements.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Walkthrough

    Uploaded by

    Aryaman Singh
    45 views9 pages
    An informal review involves a developer distributing a work product to peers for feedback, while a formal review is conducted by a team leader or moderator to identify defects. There are different types of reviews, including desk checks where peers provide informal comments, walkthroughs where the author guides an informal discussion, and inspections where a moderator leads a formal meeting to identify and log defects. Formal inspections involve preparation, an overview, page-by-page review, rework, and follow up to approval. Code reviews specifically examine source code or patches to identify defects or improvements.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    An informal review involves a developer distributing a work product to peers for feedback, while a formal review is conducted by a team leader or moderator to identify defects. There are different types of reviews, including desk checks where peers provide informal comments, walkthroughs where the author guides an informal discussion, and inspections where a moderator leads a formal meeting to identify and log defects. Formal inspections involve preparation, an overview, page-by-page review, rework, and follow up to approval. Code reviews specifically examine source code or patches to identify defects or improvements.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    45 views9 pages

    Walkthrough

    Uploaded by

    Aryaman Singh
    An informal review involves a developer distributing a work product to peers for feedback, while a formal review is conducted by a team leader or moderator to identify defects. There are different types of reviews, including desk checks where peers provide informal comments, walkthroughs where the author guides an informal discussion, and inspections where a moderator leads a formal meeting to identify and log defects. Formal inspections involve preparation, an overview, page-by-page review, rework, and follow up to approval. Code reviews specifically examine source code or patches to identify defects or improvements.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 9

    Reviews

    • A review is any activity where reviewers examine a work


    product to provide feedback.
    • You can review anything, including software requirements
    specifications, schedules, design documents, code, test plans,
    test cases, and defect reports.
    • An informal review is a written or verbal review requested by
    a developer of a work product to improve that product.
    • A formal review is a written review conducted by a team
    leader or a moderator for the purpose of identifying,
    documenting, and fixing defects in a work product.
    Types of Reviews.
    • A desk check is an informal review where the author
    distributes a work product to peers for reviews and
    comments.
    • A walkthrough is an informal review meeting, moderated by
    the author of a work product.
    • An inspection is a formal review meeting, guided by a
    moderator.
    • The meeting produces a log of identified defects in a work
    product.
    • A code review is a software inspection where defects in
    source code are identified, logged, and perhaps corrected.
    Desk Checks
    • It is useful to combine informal and formal
    reviews.
    • A desk check is the first line of defence against
    defects. You can speed up formal inspections by
    taking care of simple defects in desk checks first.
    For many work products, desk checks suffice, and
    you might not need to go to a formal inspection.
    • Desk checks are only effective if taken seriously à
    not only just say “Good…”
    Walkthrough
    • A walkthrough guides reviewers through the
    review of a work product. The author of the work
    product presents the design and ensures that the
    attendees understand its design.
    • Walkthroughs allow people with less expertise to
    review a work product
    • users of the work product are often invited to
    walkthroughs
    • Team…
    Walkthrough
    • New points-of-view often help identify defects
    • Prior to the walkthrough, the author should
    distribute presentation materials to attendees.
    • During the walkthrough, the author should
    solicit feedback from the audience.
    • After the walkthrough, the author should
    follow up with attendees who have helped out
    by giving comments
    Formal
    Inspections
    • An inspection is a formal review meeting where
    participants identify and document defects or possible
    improvements in a work product.
    • Participants aim to identify and propose ideas for
    solving defects
    • Moderator, Programmer, designer, QA Specialist
    Formal
    Inspections
    • Some steps For a formal Inspection:
    Preparation–Overview--‐Page--‐by--‐page
    Review--‐Rework--‐Follow--‐up--‐Approval
    Code
    Reviews
    • A Code Review Examines Source Code (or, More
    commonly), A Patch To identify Defects Or Possible
    improvements.
    • Source Code That Only One Person Has The expertise to
    maintain;
    • Tricky Algorithms That Are susceptible To defects;
    • Source Code That Calls difficult--‐to--‐use libraries;
    • Code written By Inexperienced developers;
    • functions That Could Fail Catastrophically If A Defect is
    present.

    You might also like