Content deleted Content added
Relationship with static and dynamic testing made evident. |
Added clarification to match Software testing article. |
||
Line 1:
'''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'', also known as [[experimentation]], [[dynamic testing]] or, simply testing. - This is good for finding faults ([[software bugs]]).
* ''Static verification'', also known as [[static code analysis|analysis]] or, [[static code analysis|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.
Line 31 ⟶ 32:
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 (not its artifacts).
== Comparison with validation ==
| |||