Before going to discuss the differences of these two u observe the fact that the client requirements may be changed on some time. Depend on the requirements we do our work .In water fall model the SDLC Phases are depend on previous Phases i.e, The output of one Phase is input to the next phase.so Whenever u do some mistake in any phase that will effects all the phases.so , whenever any modification will occur in we cant add that new requirement in the middle of the process. This is the drawback. in this model we are going in a sequential way .but the v model concept is entirely different from water fall model. Here for each and every phase there is a review . by conducting this review we can conclude that what are the new requirements , what is the effect B adding that requirement on other phases. And in this model we map the development process(verification) with testing process(validation). so for each verification there is a validation part. this is the advantage in this.
: There exists only one Test design for whole project.
: No changes can be made if customer requires it in future.
: In Waterfall Model the tester role will take place only in the test phase
but in V-Model role will take place in the requirement phase itself
: Waterfall model is a fixed process u can’t make any changes in the requirement or in any phase but in V-Model u can make any changes in the requirements
: After each is each module is tested and next module is created.
: After next module is created this module and previous module is integrated, after integrating all the modules the whole the application is tested and implemented on real time and tested for acceptance i.e testing as real time user.
: V-model is the simultaneous process but it is not in case of water fall model
: The whole application is divided into modules.
: Each module is developed and tested, each module is implemented separately on real time and gain feedback from customers and once attaining customer satisfaction we move on next module development.