V&V Concept

Before discuss this topic I need to describe the full form of V&V. V&V means are Verification and Validation. These terms are creating very confusion in Software Development Life Cycle because some people said that Verification process executes before the Validation process while some people said that it executes after the Validation. According to my understanding it always executes before the Validation process. As a word Validate and Verify describes itself because we always validate the things after the verify.

According to definition:

Verification: Am I building the right product?
Validation: Am I building the product right?
In software testing:

Verification process determines that correctness, completeness, and consistency of a program at each stage.

Validation process determines that correctness of program with respect of client requirements and needs.

Now we can come on our main topic V&V concept. V&V concept describe the practical mapping between development process and testing process. It helps to ensure that developed software meet with functional and behavioural requirements of application. Here one thing is very necessary to discuss that what things are make sure developed application meets with requirements and needs? This thing is going with Validation and Verification strategies. Verification Strategy having some processes like

  • Requirement Reviews
  • Design Reviews
  • Code Walkthrough
  • Code Inspections

and Validation having

  • Unit Testing
  • Integration Testing
  • System testing
  • End to End Testing
  • User Acceptance Testing
  • Installation Testing
  • Beta Testing

After completing these processes we can make sure that application will be meeting with the requirements and needs of application.

7 thoughts on “V&V Concept

  1. Vikas

    i am agree with your views but V&V model is a very vast topic. and very confusing term you have defined what is Verification and validation.. could you please define the V&V model?

  2. Thanks Mayank, now I am able to understand the real concept of verification and validation.

  3. meenakshi patil

    still i did not get the difference b/w v&v model can u explain me with a example in a clear n easy way.

  4. devanand

    now iam clearly understand the concept.

    thanks a lot

  5. love

    its really nice def

  6. Abhishek

    Gud job Mayank…. some more explaination of V&V Model …..

    In V&V model the testing process (Validation Part) actually starts of right from the PDP or Analyse phase of the SDLC.

    Verification & Validation actually goes hand in hand as explained below(SDLC and STLC)

    SDLC has Analyse,Design,Build and Testing Phases

    Rqrmnts Review (Analyse Phs) —–> Preparing the UAT Plan (UAT)
    Functional Specs (Analyse Phs) —–> System Test Plan
    High Level Design (Design Phs) —–> Integration Test Plan
    Detailed design & Coding (Build Phs) —–> Unit Testing

    This is actually in a form of a “V” where on one side of “V” Verification stands(Rqrmnt & fnctnl spcs) and on other side Validation stands (Testing).

  7. Suprabhat

    What are the diff. Between the v model and v&v model someone could explain it, and helps me.

Leave a Reply to devanand Cancel reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: