ravinder

• May 20th, 2006

 

In this model every phase should be implemented in a sequential manner. output of one phase should be the input for next phase.we select this model if projects is small in size and user requirements are constant . drawbacks: time consuming process. if any mistake in above phases ,same mistake will be repeated till the end of the process.This model does not allow the change of the user requirements.

Pradeep Ind

 Profile Answers by Pradeep Ind Questions by Pradeep Ind

• Nov 25th, 2006

 

The waterfall flows from top to bottom, likewise in this model the process is started when the earlier process gets completed/locked. i.e.,Requirements - Analysis - Design - Coding - Testing - Implementation This model is optimable only when the req's r clear. In this model the tester will feel the last minute pressure as he starts atlast and to deliver it to the implementation. RegardsS.Pradeep Kumar

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 27th, 2009

 

Waterfall model refers to a software development process where phases cascade downward from one to another in sequential order much like a cascading waterfall.  The phases are:  1) Requirements, 2) Design, 3) Implementation, 4) Verification, and 5) Maintenance. 

ADVANTAGES:

This model is easy to understand and provides a great deal of structure.  This process advocates a great deal of up front planning in order to be effective.  It relies on documentation which is approved and baselined.  It is not possible to proceed to a particular phase until the previous phase has met its requirements.  It is most suitable when requirements are stable and unchanging and when potential problems can be reasonably predicted. 

DISADVANTAGES:

Some say this model does not allow enough flexibility and that projects can't move forward at a satisfactory pace.  Most companies that want to turn a profit don't want to spend too much time and effort in the planning stage.  Not only that, but most software projects are complex and often change requirements or make enhancement requests throughout the development life cycle.