Verification is checking for a valid full entry. An example would be signing in with a user name and password. The system verifies that you exist in that system with a matching user name and password.
Validation is checking for the right kind of entry. Examples would be making sure what was entered are dates, numbers or an email address. If you put your age = "Bob" and your email is "12345" then the validation process will see "Bob" is not an age and "12345" is not a valid email so you will be rejected.
2007-06-05 03:03:30
·
answer #1
·
answered by rod 6
·
0⤊
0⤋
Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, and walkthroughs and inspection meetings.
Validation ensures that functionality, as defined in requirements, is the intended behavior of the product; validation typically involves actual testing and takes place after verifications are completed.
2007-06-05 11:30:42
·
answer #2
·
answered by sathiyendran a 3
·
0⤊
0⤋
In software speak, and quite briefly, validation proves that a piece of software is in proper format and *could* work. Verification proves that it *does* work.
2007-06-05 12:17:55
·
answer #3
·
answered by fjpoblam 7
·
0⤊
0⤋
Both are stupid (and terms are highly unclear).
These things start with "one MS way" when some company sells raw, not-tested product.
2007-06-05 09:08:41
·
answer #4
·
answered by alakit013 5
·
0⤊
0⤋