Software verification: Difference between revisions

Revision as of 02:30, 18 January 2019

Revision as of 02:38, 18 January 2019

Line 3:

== 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 [[1908175789212570‏<ref></ref>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.