Software walkthrough

<h2 id="process">Process</h2>
<p>A walkthrough may be quite informal, or it may follow the process detailed in IEEE 1028 and outlined in the article on <a href="/facts/Software_review/WcNas2HL">software reviews</a>.
</p>
<h2 id="objectives-and-participants">Objectives and participants</h2>
<p>In general, a walkthrough has one or two broad objectives: to gain feedback about the technical quality or content of the document; and/or to familiarize the audience with the content.
</p><p>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 as seems appropriate.
</p><p>IEEE 1028 recommends three specialist roles in a <a href="/facts/Software_review/WcNas2HL">walkthrough</a>:<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>
</p>
<ul><li>The author, who presents the software product in a step-by-step manner at the walk-through meeting, and is probably responsible for completing most action items;</li>
<li>The walkthrough leader, who conducts the walkthrough, handles administrative tasks, and ensures orderly conduct (and who is often the Author); and</li>
<li>The recorder, who notes all <a href="/facts/Software_anomaly/I1uSXySv">anomalies</a> (potential defects), decisions, and action items identified during the walkthrough meetings.</li></ul>
<h2 id="further-reading">Further reading</h2>
<ul><li>O'Regan, Gerard (2011). <a href="https://link.springer.com/10.1007/978-0-85729-172-1"><i>Introduction to Software Process Improvement</i></a>. Undergraduate Topics in Computer Science. London: Springer London. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1007%2F978-0-85729-172-1">10.1007/978-0-85729-172-1</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-0-85729-171-4. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:9037690">9037690</a>. Retrieved 2023-03-22.</li></ul>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Cognitive_walkthrough/YrkHJ01d">Cognitive walkthrough</a></li>
<li><a href="/facts/Software_review/WcNas2HL">Software review</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>IEEE Standard for Software Reviews and Audits. 2008-08-15. pp. 1–53. doi:10.1109/IEEESTD.2008.4601584. ISBN 978-0-7381-5768-9. <a href="978-0-7381-5768-9" target="_blank">978-0-7381-5768-9</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Pries, Kim H.; Quigley, Jon M. (2009). Project Management of Complex and Embedded Systems. Boca Raton, FL: CRC Press (Auerbach Publications). ISBN 978-0-429-11624-7. OCLC 297220015. <a href="978-0-429-11624-7" target="_blank">978-0-429-11624-7</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>IEEE Standard for Software Reviews and Audits. 2008-08-15. pp. 1–53. doi:10.1109/IEEESTD.2008.4601584. ISBN 978-0-7381-5768-9. <a href="978-0-7381-5768-9" target="_blank">978-0-7381-5768-9</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
</ol>

Software walkthrough open-in-new

Software walkthrough