In layman's words, if you are giving a program of addition of two numbers to the customer...
Verification is whether your s/w is adding two numbers properly.
Validation is whether customer really asked for 'Addition' program.
Verification is very obvious. Validation may sound weird but sometimes the customer's requirement is misunderstood. So, the s/w will be giving the correct result but customer is not interested in that result in first place.
2006-06-13 05:05:34
·
answer #1
·
answered by Anonymous
·
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.
2006-06-13 05:07:35
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋
Verification Means Are We Building the Product Right ?
Validation Means Are We Building the Right Product ?
2016-12-01 20:36:40
·
answer #3
·
answered by Roohi 2
·
0⤊
0⤋
VERIFICATION:
-->It makes sure that the product is designed to deliver all functionality to the customer.
Verification is done at the starting of the development process. -->It includes reviews and meetings, walkthroughs, inspection, etc. to evaluate documents, plans, code, requirements and specifications.
-->Suppose you are building a table. Here the verification is about checking all the parts of the table, whether all the four legs are of correct size or not. If one leg of table is not of the right size it will imbalance the end product.Similar behavior is also noticed in case of the software product or application. If any feature of software product or application is not up to the mark or if any defect is found then it will result into the failure of the end product. Hence, verification is very important. It takes place at the starting of the development process.
-->It answers the questions like: Am I building the product right?
-->Am I accessing the data right (in the right place; in the right way).
-->It is a Low level activity
Performed during development on key artifacts, like walkthroughs, reviews and inspections, mentor feedback, training, checklists and standards.
-->Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle.
VALIDATION:
-->Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs.
-->Validation is done at the end of the development process and takes place after verifications are completed.
-->It answers the question like: Am I building the right product?
-->Am I accessing the right data (in terms of the data required to satisfy the requirement).
-->It is a High level activity.
-->Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment.
-->Determination of correctness of the final software product by a development project with respect to the user needs and requirements.
http://www.softwaretesting-certification.com/
2015-08-19 23:22:12
·
answer #4
·
answered by John 3
·
0⤊
0⤋
verification is the process of testing u r software,whether it satisfy all its needs,
validation is the testing u r software in client environment
2006-06-13 04:58:56
·
answer #5
·
answered by cuo 1
·
0⤊
0⤋