Revision as of 00:34, 11 December 2024 edit Divinations (talk \| contribs) Extended confirmed users, Rollbackers 4,764 edits m Undid edits by 37.39.151.77 (talk) to last version by Vkuncak: unexplained content removal Tags: Undo SWViewer [1.6] ← Previous edit		Revision as of 00:35, 11 December 2024 edit undo 37.39.151.77 (talk) No edit summary Tags: Reverted Visual edit Mobile edit Mobile web edit Next edit →
Line 38: 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==

Software verification: Difference between revisions