In the basic Waterfall model process seen some disadvantages or limitations in the model which started a new SDLC model. As we seen in the Waterfall model the issues found in the end of the SDLC, this is due to the testing is occurred in the end phases of the you SDLC. To overcome this problem the V-Model is comes into the picture. It is always better to introduce testing in the early phase of SDLC, as in this model the testing activity gets started from the early phase of the SDLC.
Before starting the actual testing, testing team has to work on various activities like preparation of Test Strategy, Test Planning, Creation of Test cases & Test Scripts which is work parallel with the development activity which help to get the test deliverable on time.
V Model Software Development Life Cycle
In the V-Model Software Development Life Cycle, based on same information(requirement specification document) the development & testing activity is started. Based on the requirement document developer team started working on the design & after completion on design start actual implementation and testing team starts working on test planning, test case writing, test scripting. Both activities are working parallel to each other. In Waterfall model & V-model they are quite similar to each other. As it is most popular Software Testing Life Cycle model so most of the organization is following this model.
The V-model is also called as Verification and Validation model. The testing activity is perform in the each phase of Software Testing Life Cycle phase. In the first half of the model Verification testing activity is integrated in each phase like review user requirements, System Design document & in the next half the Validations testing activity is come in picture.
Typical V-model shows Software Development activities on the Left hand side of model and the Right hand side of the model actual Testing Phases can be performed.
In this process “Do-Procedure” would be followed by the developer team and the “Check-Procedure” would be followed by the testing team to meets the mentioned requirements.
In the V-Model software development life cycle different steps are followed however here we will taking a most common type of V-model example. The V-model typically consist of the following phases:
1. Unit Testing: Preparation of Unit Test Cases
2. Integration Testing: Preparation of Integration Test Cases
3. System Testing: Preparation of System test cases
4. Acceptance Testing: Preparation of Acceptance Test Cases
30 thoughts on “V Model”
hi,
thanking fr the more information regarding the V-V model thanks a lot
regards,
Viswanath G.
Software testing methodologies are
1)Agile
2)spiral
3)waterfall
4)scrum
5)V model
Please can I get the information on these Software testing methodologies?
very good post, i definitely love this web site, carry on it
Good article on verification & validation Model, Nice testing site to go on!!
Awesome post. Very helpful. Thanks for the info.
Fantastic List!!! Used your site to create a unique single page internet site that feels much deeper than it actually is.
Excellent Info…
nice & pretty good information on V model!! All concepts are cleared… thanks
Its give very useful information for fresher level. Can is it possible to expand information for Exp level?
Hi,
I have 1.5 years of exp. in manual testing,now i am looking change the job. sanjaykumarm@gmail.com
it is nice but i think it is better to give much more information in the form of example because by refering it we may understand it easily,thank u.
thanx for neat and understandable explanation…. thanx a lot
Thanks for understandable Details.
In the below paragraph of this article, what is the meaning of “first half of the model?”. i think you have mentioned wrong wording. because as per my knowledge, left portion is called as VERIFICATION and right one is VALIDATION. SEE BELOW PARAGRAPH OF YOUR ARTICLE.
In the first half of the model validations testing activity is integrated in each phase like review user requirements, System Design document & in the next half the Verification testing activity is come in picture.
Yes Nitin you are absolutely correct. Thanks, Updated typo in the sentence.
I agree with you Nitin, first half should be verification and second half should be validation.
Can u plz tell me the difference between V model and W model.
Thanks a lot for this contribution! It’s been very useful for me.
Nice description… Clear differentiation between Waterfall model & V – Model
Software testing methodologies are
1)Agile
2)spiral
3)waterfall
4)scrum
5)V model
Please can I get the information on these Software testing methodologies?
HI
I FOUND IT VERY INTERESTING AND HELPFUL SO I HVE SAMTHING TO PRESENT TOWOROW GODWILLINGLY
please anyone give me the case study of v model??
More useful..thanks for sharing.
Hi While development phase we are creating parallel test plans from top to buttom which seems fine but want to know the validation or testing would begin from buttom to top heriarchy like first executing unit test case then intergration test case and so?
Here in Verification Inspections and Walk-through will be there.For Validation Test Activities like Black Box testing, White Box testing etc…
If a company follow V- model and total 20 days is available to project the team for the completing the project . then after passing of 10 days client wants major changes on the requirements so as per V model .should project team accept the changes or not? Explain with reason
can you give me live example of v model in routine life
Thanks for the best explanation of V-model.