Software verification: Difference between revisions

Revision as of 14:13, 1 July 2019

Revision as of 12:13, 7 August 2019

Line 33:

== 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 42:

==See also==

{{Portal|Software Testing}}

* [[Verification and validation (software)]]

* [[Runtime verification]]