vlmadala

• Jun 8th, 2006

 

DIfference between Water fall model & W model

Waterfall model:

Based on the assumption thatrequirement will not change during the life cycle of the project, whereas requirement can change at any phase of project.

Any mistake in Requirement phase can't be recognised in water fall model untill near the end, when customer gets to see the product. This leads to huge cost of correctiveness in terms of economy.

Emphasises the developement cycle and ignores the testing cycle.

Testing merely get time as developement phase takes almost 98% of project time.

W model:

Considers the change request at every phase of the software life cycle.

reduce the probability of occuring a mistake or defect. hance saves the cost.

Gives equal importance to the testing phase as developement.

testing & developement goes parralaly.

Raghu Ram

• Jun 8th, 2006

 

Hi Friends! Before going to discuss the diffrences 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 requiremnt 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 .Thank You