In software testing terminology, validation strategy implies cross referencing the functionality of a software with the requirement specification, to assess that it adheres to the prescribed demands of the client.
Verification and validation are the two terms that go parallel. Verification states whether the specification requirements are met throughout the process of developing a product. Validation aims to check the end result of the complete process of development, to see whether the application functions as expected.
Validation is a conventional approach towards attaining a reliable product.
Typically the process of software validation strategy comprises of the following steps:
To determine whether the system performs as per the requirements and delivers the expected functionality.
Validation is carried out post verification process.
The question that flash across our minds when we talk about validation is 'are we building the right product'.
Validation involves a high level of thought process to understand and analyse whether the user requirements are met by the end product.
Why 'Validation' is important ?
A very prominent benefit of validation is that one may come across a list of failures which might have been missed out at the time of verification.
A misunderstood requirement specification may possibly be integrated into the system. This can be understood at the time of validation when differences between actual and expected results come under the scanner.
Validation activity is performed during test phases like feature testing, system testing, integration testing, load testing, stress testing etc.
Validation strategy comprises of a complete range of systems like security systems, embedded systems.