When conducting information technology projects there are several steps. The Spiral development model is one of the techniques used to build or improve information technology systems. The steps of the Spiral model are as follows: System Analysis, Design, Plan & Budget, Build, Test, and Release. These steps are repeated until the satisfactory conclusion of the project.
This model of development is best used in order to conduct life-cycle development of a system and it can be used in evolutionary development of systems. Spiral development contains a strong focus on risk management and identification process. This development process creates model prototypes of a system. This is done in order to intentionally force out the risks from system development as early. An indirect effect of Spiral development is that a program appears to be dysfunctional in the beginning.
The spiral development model has several advantages. This model is useful when a high amount of risk analysis is needed in the project and avoidance of risk must be enhanced. Spiral development is good for large and mission-critical projects in which strong approval and documentation control is needed. With spiral development a system is produced early in the project and additional functionality can be added to the system later as needed.
However, the spiral model contains significant weaknesses. This method cannot be used on small projects. When the spiral model is strictly applied, the entire scope of the project is not considered until very late in its development. Also, there is a significant chance that later when the process is repeated earlier work will be invalidated. This can cause a project to go over budget and force deadlines to move to a later date. The spiral development model is a costly development method to use because of the repeating processes and the highly specialized expertise needed to conduct risk analysis. This entire success of the project hinges on a good risk analysis when using spiral development.
The spiral development model should be used only when certain factors are in play. When developing a new system, a developer should use spiral development. When costs and risk evaluation is important Spiral development should be used. The form of development should be undertaken for medium to high-risk projects. Spiral development is useful when users are unsure of their needs or the project contains highly complex requirements. Also, the Spiral Development model should be considered when long-term project commitment is unwise because of potential changes to economic priorities or significant changes are expected.
Relational Database Theory: Riordan, Rebecca M.
What is Spiral model- advantages, disadvantages and when to use it?
I have a Masters of Science in Management with a concentration in Information Technology and Project Management. I have worked in the Project Management field for over four years.