D
dweebie
Hi,
I am slightly confused about the difference between design verification and validation, and was hoping that someone could tell me the difference between design validation and verification in connection with the following example (i.e. user need):
The product shall tolerate being dropped onto floors typical of the use environment (as this is a part of the expected use)?
When simulating the product being dropped, is this design validation? I am compelled to say yes, because the test establishes that the product is suitable for its everyday use.
However, such a need, once quantified (e.g. 15 meters onto x surface), could potentially be used as a design input (in a Product Requirement Specification), and hence, I guess, be subject to design verification. And what about the analysis supporting the test (hardness of typical surfaces, typical fall-heights...)? Could the analysis be the design validation, or is it simply a means of justifying the test e.g. 15 meters (i.e. that it is representative of the actual use) because we simulate the dropping in contrast to giving it to the users and "asking" them to drop it?
BR
dweebie
I am slightly confused about the difference between design verification and validation, and was hoping that someone could tell me the difference between design validation and verification in connection with the following example (i.e. user need):
The product shall tolerate being dropped onto floors typical of the use environment (as this is a part of the expected use)?
When simulating the product being dropped, is this design validation? I am compelled to say yes, because the test establishes that the product is suitable for its everyday use.
However, such a need, once quantified (e.g. 15 meters onto x surface), could potentially be used as a design input (in a Product Requirement Specification), and hence, I guess, be subject to design verification. And what about the analysis supporting the test (hardness of typical surfaces, typical fall-heights...)? Could the analysis be the design validation, or is it simply a means of justifying the test e.g. 15 meters (i.e. that it is representative of the actual use) because we simulate the dropping in contrast to giving it to the users and "asking" them to drop it?
BR
dweebie
Last edited by a moderator: