Applications of Verification Methods
The above three verification methods are very popular and have their strengths and weaknesses. We can compare these methods on various specific issues as given below:
| Method | Presenter | No. of Members | Pre-requisites | Report | Strength | Weakness |
|---|---|---|---|---|---|---|
| Peer reviews | 0 | 1 or 2 | No prerequisite | Not Required | Less-Expensive | Output is dependent on the ability of the reviewer |
| Walkthrough | Author | 2 to 7 members | The only presenter is required to be prepared | The report is prepared by the presenter | Knowledge sharing | Find few faults and not very expensive |
| Inspection | Author and other members | 3 to 6 members | All participants are required to be prepared | The report is prepared by the moderator | Effective but may get faults | Expensive and requires very skilled members |
Hence, Verification is likely more effective than validation but it may find some faults that are somewhat impossible to find during the validation process. But at the same time, it allows us to find faults at the earliest possible phase/time of software development.
Verification Methods in Software Verification
Reviewing any software to find faults is known as Software Verification. Verification is the process of checking that software achieves its goal without any bugs. It is the process to ensure whether the product that is developed is right or not. The reviewing of a document can be done from the first phase of software development i.e. software requirement and analysis phase where the end product is the SRS document. There are many methods for practicing the verification of the software like peer-reviews, walkthroughs, inspections, etc. that can help us in the prevention of potential faults otherwise, it may lead to the failure of the software.
Contact Us