Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code.
Verification is a static practice of verifying documents, design, code and program. It includes all the activities associated with producing high quality software: inspection, design analysis and specification analysis. It is a relatively objective process.
Verification will help to determine whether the software is of high quality, but it will not ensure that the system is useful. Verification is concerned with whether the system is well-engineered and error-free.
Type of Verification:
Walkthroughs are informal, initiated by the author of the s/w product to a colleague for assistance in locating defects or suggestions for improvements. They are usually unplanned. Author explains the product; colleague comes out with observations and author notes down relevant points and takes corrective actions.
Inspection is a thorough word-by- word checking of a software product with the intention of:
– Locating defects
– Confirming traceability of relevant requirements
– Checking for conformance to relevant standards and conventions
Inspections are more formal than walkthroughs. It involves 5 major roles:
– Author: person who originally created the work product.
– Moderator: Person responsible to ensure the discussions proceed on the productive lines.
– Reader: Person responsible for reading aloud small logical units of the work product
– Recorder: Person who records/documents all the defects that arise from the inspection team.
– Inspector: All of the inspection team members who analyze and detect the defects within the
Review is a subsequent examination of a product for the purpose of monitoring earlier changes. It is a process in which one or more persons check the changed documents or data to determine if the changes are correct. It is also an analysis undertaken at a fixed point in time to determine the degree to which stated objectives have been reached.
The process of evaluating software during or at the end of the development process to determine whether it satisfies specified requirements.
It is a dynamic mechanism of testing and validating the actual product.It always involves executing the code.It uses methods like black box testing ,white box testing and non-functional testing.Validation process describes whether the software is accepted by the user or not.