Waterfall Vs. V Model

S. No.	Waterfall Model	V-Model
1.	In Waterfall Model the tester role will take place only in the test phase.	In V-Model role will take place right from the requirement phase itself.
2.	Waterfall model is a fixed process that u can't make any changes in the requirement or in any phase.	In V-Model u can make any change in the requirements.
3.	Waterfall model is a continuous process.	V-model is the simultaneous process.
4.	Waterfall model used only after the requirements are fixed.	V-model can be used for any type of requirement (Uncertain requirement).
5.	Any mistake in Requirement phase can't be recognized in water fall model until near the end when customer gets to see the product. This leads to huge cost of correctiveness in terms of economy. So it is time consuming too.	Here for each and every phase of the software life cycle there is a review. Reduce the probability of occurring a mistake or defect. Hence saves the cost. It saves time.
6.	Emphasizes the development cycle and ignores the testing cycle. Testing merely get time as development phase takes almost 98% of project time.	Gives equal importance to the testing phase as development.
7.	Waterfall model stages: 1.User Requirement 2.System Requirement 3.Global Design 4.Detailed Design 5.Implementation 6.Testing	V model stages: 1.Component testing 2.Integration Testing 3.System Testing 4.Acceptance Testing