
- Forum
- Testing
- Software Testing
- What is V&V model?
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?...
-
08-14-2007, 02:22 AM #1
- Join Date
- Aug 2007
- Answers
- 1
What is V&V model?
What is V&v model?
How we use this in testing?
-
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
-
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!
-
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.
-
I am exactly agree with AmirG.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!
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

Reply With Quote