The spiral model starts with an initial pass through a standard waterfall life cycle, using a subset of the total requirements to develop a robust prototype.

After an evaluation period, the cycle is initiated again, adding new functionality and releasing the next prototype. This process continues, with the prototype becoming larger and larger with each iteration. Hence, the “Spiral Model.”

The theory is that the set of requirements is hierarchical in nature, with additional functionality building on the first efforts. This is a sound practice for systems where the entire problem is well defined from the start, such as modeling and simulating software.

Business-oriented database projects do not enjoy this advantage. Most of the functions in a database solution are essentially independent of one another, although they may make use of common data.

As a result, the prototype suffers from the same flaws as the prototyping life cycle described below. For this reason, the software development team has decided against the use of the spiral lifecycle for database projects.

Advantages of Spiral Model

Disadvantages of Spiral Model

When to use Spiral Model

<< Back to list all models
Tagged

Leave a Reply

Your email address will not be published. Required fields are marked *