Software verification: Difference between revisions

Revision as of 17:32, 16 April 2021

Revision as of 15:06, 3 August 2023

Line 1:

'''Software verification''' is a discipline of [[software engineering]], [[programming languages]], and [[theory of computation]] whose goal is to assure that software fully satisfies all the expected requirements.

== Broad scope and classification ==

A broad definition of verification makes it equivalentrelated 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 (computer science)|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.

Under the [[ACM Computing Classification System]], software verification topics appear under "Software and its engineering", within "Software creation", whereas [[Program verification]] also appears under [[Theory of computation]] under Semantics and reasoning, Program reasoning.

== Dynamic verification (Test, experimentation) ==