In the last topic we learned about forms of testing. And In this topic we will learn what a Walkthrough is. Walkthrough is an evaluation process which is an informal meeting, which does not require us to prepare anything. In this we will showcase the product and any participants that have come for the meeting, they will give their comments there. What will be the result of it? Any information of the participants, which are coming in the comments, that we will use as information, to better the product. Why is Walkthrough important? Walkthrough is important for a high-level document which is called Requirement Specification which is important for any architectural document. Come, let’s take an example of SRS, System Requirement Specifications. In this we will take the requirement of the complete system. What are the modules that will interact with each other, which database we are using, which server we are using? All these things we will note down in a particular document. And we will do a Walkthrough for that. If someone has any information or any participant is giving any good suggestions then we will change it. Keep in mind that this is Static Testing that is happening, in this all the testing is happening on the documentation. What are the goals of Walkthrough? All the documentations that are there, we will present them to the stakeholders and we will take information from that whether anything is missing in the documentation or somewhere we have to correct it. We will explain and evaluate every term of the document. We will keep a common understanding of documents and products. We will examine and discuss whatever solutions we have provided, is there any other alternative for that or not. Imagine that we have taken a server because of which our costing is increasing, is there any other alternative for that, where we take another server and our cost is effective. All these things and all these points, those we will include in Walkthrough. What did we learn, we learned about Walkthrough, why is Walkthrough important, what we will do in Walkthrough and what is the output of Walkthrough? In the next topic we will see Code Review.
Share a personalized message with your friends.