Question

what is inspection, walkthrough and Desk checking testing

my course is analysis and design and it's not shows in the subject so i choose operation management just to complete the process !!!

Answer 1

INSPECTION

Inspection is the most formal review type usually led by a trained moderator. During an inspection, the documents are prepared and checked rigorously by the reviewers before the meeting. They compare the work product with its sources and other referenced documents using rules and checklists. In the inspection meeting, the defects found are documented in a logging list. Depending on the organization and objectives of the project, the inspection can be balanced to serve specific goals such as-

• to assist the author in enhancing the quality of the document under inspection.
• removes defects efficiently and as early as possible and prevents the occurrence of similar defects.
• to improve product quality.
• creates a common understanding by exchanging information.

WALKTHROUGH

A walkthrough in software testing is conducted by the author of the document under review with peers, managers, and fellow team members to achieve a common understanding and to gather feedback. A walkthrough can be pre-planned or organized based on the requirement. The participants are selected from different backgrounds and departments to have a diverse point of view to a common objective. A walkthrough is specifically used for high-level documents such as requirement specifications and architectural documents. The specific goals of walkthrough are-

• Collecting information concerning the topic in the document and presenting the document to the stakeholders, both within and outside the software discipline (Economic times, 2020).
• to explain and evaluate the content of the document.
• to establish a common consensus on the document.
• to examine and analyze the different solutions and possible alternatives.

DESKCHECKING

A desk checking is a manual process in which the programmer runs through lines of code to identify errors and to check logic before the program is launched. The goal of desk checking is to inspect the solution as fast as possible and do quick changes if necessary without the code leaving the developer's local machine. Desk check also facilitates shared accountability on quality. It is quick and inexpensive.