continuing on from one of my team mates blog’s, I wish to develop further on a particular model type within our designated categories : ” The Spiral Model”
This model type is a newer version of the “Waterfall Model”. It combines some key aspects of the waterfall model and rapid prototyping methodologies.
The “Waterfall model” is the most simple and widely accepted/followed software development model, but like any other system, this does have its own pros and cons. Spiral model was designed in order to overcome the disadvantages of the waterfall model.
Waterfall model is one of the oldest and simplest models designed and followed during software development process. But the model has its own disadvantages such as there is no fair division of phases in the life cycle, not all the errors/problems related to a phase are resolved during the same phase, instead all those problems related to one phase are carried out in the next phase and are needed to be resolved in the next phase, this takes more time for the next phase to solve them. The risk factor is the most important part, which affects the success rate of the software developed by following this model.
In order to overcome the cons of the above model, it was necessary to develop a new Software Development Model, which could help in ensuring the success of a software project. One such model was developed which incorporated the common methodologies followed in the waterfall model, but it also eliminated almost every possible/known risk factors from it. This model is referred to as the “Spiral Model” or “Boehm’s Model”. Read more at Buzzle: http://www.buzzle.com/editorials/1-13-2005-64082.asp