Waterfall and Whirlpool software development models.

Waterfall
The waterfall development model is designed so that you only have to go through every part of the design process once. For each and every step you have to make sure that every little thing is finished before proceeding onto the next. The greatest strength of this method is the fact that you have to be very thorough and analyse every part of each section because it will be the only chance you get before moving onto the next part. It is also argued that it makes the development of a project cheaper as it is said to be quicker. this is because as each problem develops, it should have been found at its most basic stage, and therefore at its easiest to fix. This in turn makes the whole process more efficient.

Whirlpool
In the whirlpool development model you begin the development at one point which you keep cycling back to. With this model you constantly re-evaluate and re-develop all aspects of your design until you are happy with it all, instead of each piece individually one after the other. The downfall of this model however is that it takes quite a lot of time to keep going back over the same aspects over and over improving them each time. This also makes it hard to time manage as it is hard to say how many more cycles it will take to complete the product, unlike the waterfall method, where you can clearly see how much of the project is complete and what is left to do.

Both have their strengths and weaknesses. Personally I think that the Whirlpool method of development will work best when making a website. This is because it is very hard to get things 100% perfect in each stage so that you can progress onto the next. Also, as you are constantly getting new feedback from the client and others, different parts will need to be changed from each stage. This will really scrap the waterfall method from use.