Code walkthrough is carried out to detect the presence of algorithmic and logical errors in the code.
Code walkthrough can be considered as an informal code analysis technique.
After the module has been coded, compiled and all syntax errors has been removed then the code walkthrough is carried out. A few developers of the development team are given the code couple of days before the walkthrough meeting. Each member selects few test cases and simulates execution of the code by hand.
The members note down their findings during code walkthrough and discuss them in the meeting where coders of the modules are present.
Even though code walkthrough is an informal analysis technique, several guidelines has evolved over the years for making this naive but useful analysis technique more effective.
These guidelines are based on the personal experience, common sense, several other subjective factors as well. Therefore these guidelines should be considered as examples rather than accepted as rules to be applied dogmatically.
Some of these guidelines are given below:
The team performing code walkthrough should not be either to big or too small.
Discovery should focus on discovery of errors and avoid deliberations on how to fix the discovered error.
In order to foster cooperation among engineers and avoid the feeling that they are being evaluated in the code walkthrough meetings, managers should not attend the walkthrough meetings.