As a software developer, I participated in different types of walkthroughs. - use case walkthrough A use case would be presented first in general, then step by step. - code walkthough A code module would be presented (summarized) first in general, then code block by code block.

Yes a walkthrough could apply to presenting a software productive in an interactive way with the client. The client walks through parts with the demonstrator. The term walkthrough originated when rehearsing a play or dance on stage. The walkthrough is not a practice performance, but the actors, dancers or whatever moving around on stage in the right sequence and position to see how the stage will be traversed, and how the production fits on it. It includes coming on from back stage, and exiting again. Walkthrough is like a guided tour of something operating. Rather than simply watching it operate, someone would narrate and describe the steps of the operation, the performance or whatever. Here is an example: A director of a stage show could say "When the singers walk on stage, you need to turn around and walk to the middle of the stage..let's walk through those actions...". A computer applications engineer could say "you can see at this stage of the program, the client could add a new field to suit their database requirements like this..."(does action to demonstrate) "so you try that now". So walkthrough as a term could be used in a broad range of situations, but is like a demonstration of steps where the operation is explained, but not demonstrated as running in correct time necessarily.