Software Validation Vs Verification. The goal of validation is an actual product. Whereas verification takes place while the product is still under development validation is performed upon the completion of a given module or even the completion of the entire application.
In other words Validation intends to fulfill the intended wishes of user when placed under intended environment whereas Verification intends to check if the requirements of the phases are met. Verification is all when you are yet to eat but are checking on a few things by reviewing the subjects. In other words software verification ensures that the output of each phase of the software development process effectively carry out what its corresponding input artifact specifies requirement - design - software product while software validation ensures that the software product meets the needs of all the stakeholders therefore the requirement specification was correctly and accurately expressed in the first place.
Verification is the checking specifications as per requirements while validation is the checking of the software either it meets the customers requirements.
Verification activities are fairly straightforward and often done via automation. In other words software verification ensures that the output of each phase of the software development process effectively carry out what its corresponding input artifact specifies requirement - design - software product while software validation ensures that the software product meets the needs of all the stakeholders therefore the requirement specification was correctly and accurately expressed in the first place. Validation focuses on ensuring that the stakeholder gets the product they wanted. In my opinion software verification is the mark of the professional developer.