Software verification


Software verification is a discipline of software engineering whose goal is to assure that software fully satisfies all the expected requirements.

Broad scope and classification

A broad definition of verification makes it equivalent to software testing. In that case, there are two fundamental approaches to verification:
Dynamic verification is performed during the execution of software, and dynamically checks its behavior; it is commonly known as the Test phase.
Verification is a Review Process.
Depending on the scope of tests, we can categorize them in three families:
The aim of software dynamic verification is to find the errors introduced by an activity ; or by the repetitive performance of one or more activities.

Static verification (Analysis)

Static verification is the process of checking that software meets requirements by inspecting the code before it runs. For example:
Verification by Analysis - The analysis verification method applies to verification by investigation, mathematical calculations, logical evaluation, and calculations using classical textbook methods or accepted general use computer methods. Analysis includes sampling and correlating measured data and observed test results with calculated expected values to establish conformance with requirements.

Narrow scope

When it is defined more strictly, verification is equivalent only to static testing and it is intended to be applied to artifacts. And, validation would be equivalent to dynamic testing and intended to be applied to the running software product. Notice that requirements validation can be performed statically and dynamically.

Comparison with validation

Software verification is often confused with software validation. The difference between verification and validation: