Tuesday 7 June 2011

Verification and Validation:

           Verification
               Validation

(1) Verification is done to ensure that the work product of a given phase of the development cycle fulfill the specifications established during prior phase.

(1) Validation is the process of evaluating software at the end of the software development process to determine compliance with the requirements.

(2) Verification: Are we producing the product right?

(2) Validation: Are we producing the right product?

(3) In verification un-covering of defects will be done in primary ways. Here no code will be executed. Before building actual system this checking will be done. This process will be called Quality Assurance.

(3) Validation concern checking will be done by executing code for errors(defects). This also can be called as Quality control

(4) Verification is nothing but the static testing.

(4) Validation is nothing but the Dynamic testing.

(5) Verification is done before validation.

(5) Validation cannot be done before verification.

(6) Inputs to the verification are check list, issue list, walkthroughs and inspection meetings, reviews and meetings.

(6) Input on the validation on the other hand is the actual testing of an actual product.

(7) Output of the Verification is a nearly a perfect set of documents, plans, specifications and requirements document.

(7) Output of the validation on the other is a nearly perfect actual product.

                                                        
                                                 

No comments:

Post a Comment