Software verification: Difference between revisions

Revision as of 21:02, 22 May 2017

Latest revision as of 18:46, 23 June 2025

(26 intermediate revisions by 21 users not shown)

Line 1:

{{Short description|Verification that software meets requirements}}

'''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) ==

Line 34 ⟶ 37:

== 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 (of the whole software product) would be equivalent to dynamic testing and intended to be applied to the running software product (not its artifacts, except requirements). Notice that requirements validation can be performed statically and dynamically (See [[Software verification and validation#Artifact_or_specification_validationArtifact or specification validation|artifact validation]]).

== 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 specifications? (As a house conforms to its blueprints.)

Line 43 ⟶ 46:

==See also==

{{Portal|Software Testing}}

* [[Verification and validation (software)]]

* [[Runtime verification]]

* [[Hardware verification]]

* [[Formal verification]]

== References ==

* [[IEEE]]: ''SWEBOK: Guide to the Software Engineering Body of Knowledge''

* [[Carlo Ghezzi]], [[Mehdi Jazayeri]], [[Dino Mandrioli]]: ''Fundamentals of Software Engineering'', Prentice Hall, {{ISBN |0-13-099183-X}}

* [[Alan L. Breitler]]: ''A Verification Procedure for Software Derived from Artificial Neural Networks'', Journal of the International Test and Evaluation Association, Jan 2004, Vol 25, No 4.

* Vijay D'Silva, [[Daniel Kroening]], Georg Weissenbacher: [http://www.kroening.com/papers/tcad-sw-2008.pdf A Survey of Automated Techniques for Formal Software Verification]. IEEE Trans. on CAD of Integrated Circuits and Systems 27(7): 1165-1178 (2008)

[[Category:Software testing]]