Waterfall and Whirlpool software development

The ‘waterfall’ model has been around for many years and at the early stages of the software development it was recognised as the main model for many systems. In addition the solution offered steps by providing requirements early. I.e. Every stage is approached, completed and signed off before moving onto the next step.
However this model was also made with the intension of being able to ‘Freeze’. Subsequently this allowed anyone to stop the process and move onto the next one. The advantage of this model was that it allowed you to manage it with control but was hard to go back if you had to make any drastic changes.





The ‘Whirlpool’ model has a much better system than the ‘Waterfall’ model due to allowing changes over and over again. As a result this holds no restrictions when it comes to the process which allows a more in-depth approach allowing such problems as expense and errors being notified before action are approached. Also it allows you to work on more than one section at a time and has no problems if you went back and made changes.
I would use the ‘Whirlpool’ if I was to produce a website due to the flexibility it occurs. I.e. it would allow me to go back on designs and change them as building blocks, providing a more in-depth approach. Also it would provide me with the option of working on one stage at a time.