a verification and validation technique that consists of producer of a work product (e.g., document, software component) leading a set of evaluators though the contents of the work product in order to train them and to solicit comments and recommendations. Note that the walkthough of an executable software unit may involve the manual testing of the unit by mentally executing test cases. Contrast with audit, inspection, and review.
An inspection of the building site by the architect, owner and/or the general contractor.
(General:) A thorough demonstration or explanation that details each step of a process. (In user testing:) A peer review of a product created during the systems development process, with the goal to identify errors and learn from users' experiences.
(Computer System Development) A peer review of a system design, code, etc. The goal is to identify errors as early as possible and learn from other people's experience. Managers and people who prepare performance reviews should NOT be in the room. The concept is to invite "egoless" constructive criticism and to nurture team-oriented validation and debug responsibility. (Telecommunications) 5-digit code used to access an IEC. Requires Feature Group B or (See Bypass, CIC Code, Casual Calling).
The seller invites the buyer to inspect the property and a list of items to be repaired or replaced will be agreed. Normally takes place after the home inspection.
an explanation and defense of the program's algorithm and implementation to an audience
an informal review in which the author of a work product describes it to a group of peers and solicits their comments
a review in which the meeting consists of a presentation by the producer
The designer, architect, contractor and/or subcontractors meet at the project site to evaluate the project and scope of work.
An informal way of presenting a technical document in a meeting. Unlike other kinds of reviews, the author runs the walkthrough: calling the meeting, inviting the reviewers, soliciting comments and ensuring that everyone present understands the work product. It typically does not follow a rigid procedure; rather, the author presents the work product to the audience in a manner that makes sense. Many walkthroughs present the document using a slide presentation, where each section of a work product is shown using a set of slides. Work products that are commonly reviewed using a walkthrough include design specifications and use cases.
A review of requirements, designs or code characterized by the author of the material under review guiding the progression of the review.
A walkthrough is a term describing the consideration of a process at an abstract level. The term is often employed in the software industry (see software walkthrough) to describe the process of inspecting algorithms and source code by following paths through the algorithms or code as determined by input conditions and choices made along the way. The purpose of such code walkthroughs is generally to provide assurance of the fitness for purpose of the algorithm or code; and occasionally to assess the competence or output of an individual or team.