Waterfall VS Whirlpool Software Models

In the early stages of software development it was recognised as the main model for many systems. The solution offered steps early providing requirements early. Each of the various stages is approached, completed and signed off before moving onto the next step.

This model also was made with the intension of being able to ‘Freeze’. This allowed anyone to stop the process and move onto the next one. This in my opinion can cause allsorts of problems varying from design changes to time management errors e.g. imagine freezing a construction of a building and going back to it later with a different approach.

The ‘Whirlpool’ model has a much better system than the ‘Waterfall’ model as it allows changes over and over again. 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.

In comparison the Whirlpool I think is a better approach if I were to use if for a website. This process would allow me to go back on designs and implement them as building blocks providing a more in-depth approach. This would provide me with the option of working on one stage at a time.

Whereas if I used the ‘Waterfall’ process, I would be able to get a good idea of my website process before any actions but doesn’t allow any options for major changes. Only the option to ‘Freeze’ my design, but the downside is I can’t change anything in the design.
The Whirlpool software development process can be used in Web Design.

Brief
Research
Development
Design
Implementation
Testing
Deploy
Maintenance