Exforsys
Results 1 to 5 of 5

What is V&V model?

This is a discussion on What is V&V model? within the Software Testing forums, part of the Testing category; What is V&v model? How we use this in testing?...

  1. #1
    prasad_chawan9 is offline Junior Member Array
    Join Date
    Aug 2007
    Answers
    1

    What is V&V model?

    What is V&v model?
    How we use this in testing?

  2. #2
    bharathp is offline Member Array
    Join Date
    May 2006
    Location
    Banglore,India
    Answers
    83
    Hi

    V&V Nothing But "V Model" in software life cycle

    here V&V stands for "Verification&Validation"




    http://groups.google.com/group/testi...ications?hl=en

    TestBharath

    Regards,
    Bharath

  3. #3
    AmirG is offline Junior Member Array
    Join Date
    Nov 2008
    Answers
    1
    The V&V model explains the activities that are carried out during verification and validation. Basically, verification methods are static, i.e. the code is not executed.
    Verification methods are reviews, inspections, code walkthroughs, etc...
    Validation activities include executing the code, in unit testing, integration testing, system testing, acceptance testing, etc...

    Good luck!

  4. #4
    tester70 is offline Member Array
    Join Date
    Jun 2010
    Answers
    42

    V model

    The V-model is a software development model which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing.

  5. #5
    Acelya is offline Junior Member Array
    Join Date
    Jul 2010
    Answers
    5
    Quote Originally Posted by AmirG View Post
    The V&V model explains the activities that are carried out during verification and validation. Basically, verification methods are static, i.e. the code is not executed.
    Verification methods are reviews, inspections, code walkthroughs, etc...
    Validation activities include executing the code, in unit testing, integration testing, system testing, acceptance testing, etc...

    Good luck!
    I am exactly agree with AmirG.

    And I want to add a few things.

    V&V means Verification and Validation.

    Validation is genarally done after the testing phase. Because it is done with customer. Actually in validation the aim is: looking project to understand whether the project is matching with the customer need/want or not.

    Verification can be done in every phase because it doesn't use the code execuation. It is done by looking code directly. And its aim is: Developer determine his/her aim at the begining of the each phase. And at the end of the each phase he/she verificate the project to understand that he/she can meet his/her aim or not.

    I hope I can explain the main logic of them and their differences. Sorry if I made mistakes in my sentences (English)

    Best regards,

    Acelya

    •    Sponsored Ads