Jump to content

Software verification

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by George Rodney Maruri Game (talk | contribs) at 05:44, 11 May 2017 (Relationship with static and dynamic testing made evident.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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

There are two fundamental approaches to verification:

  • Dynamic verification, also known as experimentation, dynamic testing or, simply testing. - This is good for finding faults (software bugs).
  • Static verification, also known as analysis or, static testing - This is useful for proving the correctness of a program. Although it may result in false positives when there are one or more conflicts between the process a software really does and what the static verification assumes it does.


Dynamic verification (Test, experimentation)

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:

  • 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)

The aim of software dynamic verification is to find the errors introduced by an activity (for example, having a medical software to analyze bio-chemical data); or by the repetitive performance of one or more activities (such as a stress test for a web server, i.e. check if the current product of the activity is as correct as it was at the beginning of the activity).

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.

Comparison with validation

Main article: Software verification and validation

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.

See also

References

Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_verification&oldid=779821953"