Content deleted Content added
m Phrases about a more general issue moved to its own section. |
|||
Line 4:
* ''Dynamic verification'', also known as Test or [[Experimentation]] - This is good for finding bugs
* ''Static verification'', also known as [[Static code analysis|Analysis]] - This is useful for proving correctness of a program although it may result in false positives
== Dynamic verification (Test, experimentation) ==
Line 19 ⟶ 20:
** Non functional test (performance, [[stress testing (software)|stress test]])
The aim of software dynamic 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.▼
Software verification is often confused with software validation. The difference between [[Verification and validation (software)|''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.
== Static verification (Analysis) ==
Line 33 ⟶ 31:
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'' 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==
| |||