As per IEEE, “Verification is the process of evaluating the system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase” [IEEE01].
In general, software verification is the process by which we determine whether the software built meets the expected requirements without actually executing the code.
In software verification, we review the documents and perform walkthroughs of the code to find faults in the system in the early stages of development. The verification process aims to ensure the quality of the design, architecture, and overall software.
The most commonly used verification methods are:
Peer reviews
Walkthroughs
Inspection
In peer reviews, other developers review the documents to find faults in the system. This activity aims to have a low cost, high quality, and high degree of effectiveness.
During this process, the software requirements verification (SRS) document is reviewed in detail. It is an informal activity, and it provides the best results only if the reviewer has the following:
In walkthroughs, the author prepares for the meeting and presents the document to a small group.
The author then distributes the document to the team and introduces the material to familiarize people with the document.
All the participants can ask questions, discuss the product’s functionality, and then write the faults and defects in a report. At the end of the meeting, the author writes a detailed report about the error or faults identified in the meeting.
Inspections are formal reviews where a group of trained professionals reviews the code and the design. The members of the review group are not on the development team.
Free Resources