<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by krish_prasad: Hi
Can anyone help me in understanding this concept. If you can please give me information of any web site which has a write up on this.
The objective of Validation is to produce documented evidence, which provides a high degree of assurance that all parts of the facility will consistently work correctly when brought into use. This involves reviews of specification, design and construction and testing (qualifications: installation, operation and performance).
Fundamental principle behind this is that quality has to be build in the proces to come to the system; and not only by testing.
Validation also means keeping the system in the validated state (for example change control).
Interesting subjects are GAMP (good automated manufacturing practices) and SLC (system life cycle)
I think the Verification is a company action to verificate the product, and the Validation is a customor action to validate the product. I think that Validation is likely to explain with the acceptance testing.
Validation" is the process of evaluating the software at the end of the software development to ensure compliance with the software requirements. Testing is a common method of validation.
Verification" is the process of determining whether or not the products of a given phase of software development fulfill the specifications established during the previous phase. The verification activities include proving, testing and reviews
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by winguy: Validation" is the process of evaluating the software at the end of the software development to ensure compliance with the software requirements.<HR></BLOCKQUOTE>
Wrong. Valadation is an activity from the beginning til the end: from validating user requirement specification, till design, test and qualification.
Interesting that there are still so many definitions and all different.