Well, even though people say things like "we're using the RUP", they're too often just doing big design up-front and stumbling in their false sense of security. There are different shades of waterfall -- sometimes you have only 1 design phase after which you can't touch the design models without losing a member, sometimes you have a second "iteration" which proves to be of little or no worth because you're already too deep in the swamp. There are differences in the prescribed process and the described process -- the company pays 000000s for RUP and the like but fail to actually follow the process. (then again, most processes are based on a series of very small waterfalls so you could basically claim that most software processes are shades of the waterfall...)
I want to know where it is used in software engineering world ? People prefer RUP , isn't?
Product development is just like any other genre of software development -- some product development companies are more waterfallish than others.
Originally posted by Pradeep Bhat:
What about product development ? Do they fall into waterfall model.
Product development can be handled using either Iterative or Waterfall methodology or may be a mix of 2
Originally posted by Lasse Koskela:
Yep, and whoever figures out the exact formula and manages to prove it gets filthy rich.
Originally posted by Zubair Mushtaq:
well as i have read water fall model is suitable for the situations in which u are very clear about requirements
and need to fully comlete a phase b4 goingt o next phase
Originally posted by Ilja Preuss:
Why would you ever need to do this?