Content deleted Content added
No edit summary Tags: Reverted Visual edit Mobile edit Mobile web edit |
RandFreeman (talk | contribs) Adding local short description: "Verification that software meets requirements", overriding Wikidata description "overview of techniques for verifying software" |
||
| (4 intermediate revisions by 2 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 satisfies the expected requirements.
Line 38 ⟶ 39:
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 validation|artifact validation]]).
== Comparison with validation ==
{{Main|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.)
* Software ''validation'' asks the question, "Are we building the right product?"; that is, does the software do what the user really requires? (As a house conforms to what the owner needs and wants.)
==See also==
| |||