Software Verification - Dynamic Verification (Test, Experimentation)

Dynamic Verification (Test, Experimentation)

Dynamic verification is performed during the execution of software, and dynamically checks its behaviour; 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:

• Test in the small: a test that checks a single function or class (Unit test)
• Test in the large: a test that checks a group of classes, such as
  • Module test (a single module)
  • Integration test (more than one module)
  • System test (the entire system)
• Acceptance test: a formal test defined to check acceptance criteria for a software
  • Functional test
  • Non functional test (performance, stress test)

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

• Software verification asks the question, "Are we building the product right?"; that is, does the software conform to its specification.
• Software validation asks the question, "Are we building the right product?"; that is, is the software doing what the user really requires.

The aim of software verification is to find the errors introduced by an activity, i.e. check if the product of the activity is as correct as it was at the beginning of the activity.