{{unreferenced, date=June 2014 A reverse walkthrough is a process in which the reader or consumer of a technical product takes the author through it. A reverse walkthrough is a confirmation that the consumers of a technical product have the same understanding as the author of that product. The author(s) ask questions about the content to confirm that the reader has understood it. This is common in

software engineering Software engineering is a systematic engineering approach to software development. A software engineer is a person who applies the principles of software engineering to design, develop, maintain, test, and evaluate computer software. The term '' ...

for software reviews or

use case In software and systems engineering, the phrase use case is a polyseme with two senses: # A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful. # A potential scenario ...

business process A business process, business method or business function is a collection of related, structured activities or tasks by people or equipment in which a specific sequence produces a service or product (serves a particular business goal) for a parti ...

reviews when the developer reads the source/use case/process back to the author. The reverse walkthrough should be made when the consumers of the technical product have reviewed it and there is a risk that their understanding may not be reflective of the original intent.

Terms used here

"Technical Product" here can refer to a workflow, software code, use case specification or diagram that is fairly complex. Consumers of a technical product are those engineers that need to interpret the code, specification or diagram.

Objectives and participants

A reverse walkthrough is meant to confirm a common understanding about the contents from consumers of a technical product. Often the author may ask, "what is meant by __" or "how will you implement this flow?". A walkthrough is normally organized and directed by the author of the technical document. Any combination of interested or technically qualified personnel (from within or outside the project) may be included, such as the Analyst, Designer, Architect, Developer and Quality Assurance engineers.

Terms used here

Objectives and participants

See also