Re: What is the difference between D&D Review, D&D Verification and D&D Validation?
Potdar, I am with you on the design review stage, I would just add that it is normal to have people from various parts of the organisation involved e.g. purchasing, so they can comment on things such as 'lead times' and costs of materials. The aim being to prevent potential problems.
I am also with you on verification, usually involving tests on prototypes, alternative calculations etc.
I would look at validation differently though. I believe that validation can only be done on the 'finished product. e.g. if the automobile was verified on prototypes, we can only do the validation on the product that actually comes off the line. Or, if it is software we have designed, validation can only be done when it is installed on the user's own system. Additionally, if you then sell that software to someone else, you would have to re-validate it on their system.
I also agree that sometimes verification and validation may have to be done at the same time.