|
60 | 60 | specifically. |
61 | 61 |
|
62 | 62 | To "validate" is to assess the overlap between a human need and a |
63 | | -product that solves that need. It answers the question "are we correctly |
64 | | -solving the actual problem"? To "verify" is to ensure that the product |
65 | | -is being built correctly and with high quality, based on best practices, |
66 | | -regulations, and specifications. It answers the question "are we |
67 | | -developing the solution correctly"? An easy way to tell them apart is |
68 | | -that you can often make the verification process automatic, while you |
69 | | -often need to have extensive manual evaluation, judgment, and review for |
70 | | -the validation process. |
| 63 | +product that solves that need. It answers the question "have we selected |
| 64 | +the correct solution to solving the actual problem"? To "verify" is to |
| 65 | +ensure that the solution is being built correctly and with high quality, |
| 66 | +based on best practices, regulations, and specifications. It answers the |
| 67 | +question "are we developing the solution correctly"? An easy way to tell |
| 68 | +them apart is that you can often make the verification process |
| 69 | +automatic, while you often need to have extensive manual evaluation, |
| 70 | +judgment, and review for the validation process. |
71 | 71 |
|
72 | 72 | Sometimes, these two overlap, but often they don't. For example, if you |
73 | 73 | are involved in creating a specification that accurately describes |
|
0 commit comments