What is Walkthrough in software testing?

 Walkthrough:

• It is not a formal process/review
• It is led by the authors
• Author guide the participants through the document according to his or her thought process to achieve a common understanding and to gather feedback.
• Useful for the people if they are not from the software discipline, who are not used to or cannot easily understand software development process.
• Is especially useful for higher level documents like requirement specification, etc.

The goals of a walkthrough:

1. To present the documents both within and outside the software discipline in order to gather the information regarding the topic under documentation.
2. To explain or do the knowledge transfer and evaluate the contents of the document
3. To achieve a common understanding and to gather feedback.
4. To examine and discuss the validity of the proposed solutions 
5.  
6.  
7. Technical review:
   
8. It is less formal review
9. It is led by the trained moderator but can also be led by a technical expert
10. It is often performed as a peer review without management  participation
11. Defects are found by the experts (such as architects, designers, key users) who focus on the content of the document.
12. In practice, technical reviews vary from quite informal to very formal

The goals of the technical review are:

1. To ensure that an early stage the technical concepts are used correctly
2. To access the value of technical concepts and alternatives in the product
3. To have consistency in the use and representation of technical concepts
4. To inform participants about the technical content of the document