A: This was a similar question that I had regarding design verification and validation. Both served the same purpose as well as underwent similar processes in order to achieve the desired result. What I  considered a major difference between the two would be the true words "verification" and "validation". In the design verification, the sole premise is the checking portion of the PDCA. That involves making sure that the input matches the output. During the verification report, researchers take all the test results and put them in the report itself, and they show everything that passed or failed in the designing of the product. In the design validation, the intent is that the input matches what the demographic needs and what the intended use of the product has is true to form. This involves the testing phase of the product itself. The other point that sets these two apart is that the validation process is not truly necessary if the verification process is done correctly. The validation of the device would entail using the device on living people, a cadaver, or having a physician try to use the product. 

While watching this week's lecture on design control, I tried to figure out the main difference between Design Verification and Design Validation. Both are used to make sure that the design outputs align with the design inputs. They both must also be documented in the Design History File (DHF). Why are these two sections separate though because they seem to share similar purposes. Hopefully someone can clarify this with more details. Thank you!

The main difference between the two is that verification is compare the beginning to the end. Did you accomplished the things you stated at the begin. While validation is more so does this production accomplish the goal it was intend before. It may not work the same way but it does do what it is suppose to do.

While watching this week's lecture on design control, I tried to figure out the main difference between Design Verification and Design Validation. Both are used to make sure that the design outputs align with the design inputs. They both must also be documented in the Design History File (DHF). Why are these two sections separate though because they seem to share similar purposes. Hopefully someone can clarify this with more details. Thank you!

Design Validation decides whether you are building the right product. Validation is the method involved with checking whether the determination catches the client's prerequisites, while verification is the most common way of making sure that the product meets particulars. Verification incorporates every one of the exercises related to delivering excellent programming.