-In this case, I think about the spiral model, - -2
-and evolutionary prototyping model will work. Definitely you don't want to - -3
-have a pure water from water. Why? Well because it - -4
-is very expensive with a pure waterfall model to make - -5
-changes during the course of the project, especially changes - -6
-that involve requirements. Why? Because we saw that it can - -7
-be very expensive. Whereas with the spiral model, we saw - -8
-that being iterative, we can actually make correction throughout development. - -9
-Similarly, with evolutionary prototyping, we keep evolving our system - -10
-based on the customer feedback. And therefore, if something changes, - -11
-we will get feedback right away, and we will - -12
-be able to adapt. So the key thing here is - -13
-that anything that is iterative works better in the - -14
-case of changing environments. So, situations in which your requirements, - -15
-the situation, the project might change. Whereas waterfall is - -16
-more appropriate for situations in which the requirements are stable, - -17
-we know the domain, and possibly we also know the technologies involved. -- cgit 1.4.1