Spiral Model Advantages and Disadvantages
This article is aimed at providing information on the advantages and disadvantages of spiral model.

Also termed as spiral life cycle model, it can be defined as a model based on SDLC, or systems development life cycle model. It integrates characteristics of waterfall model and prototyping model. SDLC is simply a model that provides procedure and guidelines for various phases of software development, such as requisite, architecture, application and testing followed by maintenance. Waterfall model is defined as a method of sequential and linear advancement of a software. Prototyping model is building and testing of a required prototype development.
Procedure for Development
There are several advantages and disadvantages of spiral model, which should be considered before finalizing on the implementation. The overview of steps in developing a spiral life cycle model can be given as below.
Step 1: The requisites of the new system are described in depth, by consulting all the users of the existing model and an introductory system design is prepared for new model or system.
Step 2: First archetype is built up with features close to the final system, followed by creating second type.
Step 3: Creating second prototype involves evaluating the performance of the first and describing the requisites of the second prototype, followed by building and testing the second architecture.
Step 4: The discrepancies in the estimated running cost are evaluated and the efficiency of the new prototype is tested to find out if the new model meets the expectations of the customer.
Step 5: The steps in creating new prototype are repeated till the new prototype fulfills all the demands or requisites desired by the customer.
Step 6: Maintenance of the new model is done to avoid break down, till it is assured that the new system is working smoothly.
Just like any other system or model, a client should evaluate the pros and cons. Let's go through these quickly.
Advantages
- Repeated or continuous development helps in risk management. The developers or programmers describe the characteristics with high priority first and then develop a prototype based on these. This prototype is tested and desired changes are made in the new system. This continual and steady approach minimizes the risks or failure associated with the change in the system.
- Adaptability in the design in software engineering accommodates any number of changes, that may happen, during any phase of the project.
- Since the prototype building is done in small fragments or bits, cost estimation becomes easy and the customer can gain control on administration of the new system.
- As the model continues towards final phase, the customer's expertise on new system grows, enabling smooth development of the product meeting client's needs.
- The models work best for large projects only, where the costs involved are much higher and system pre requisites involves higher level of complexity.
- Itl needs extensive skill in evaluating uncertainties or risks associated with the project and their abatement.
- It works on a protocol, which needs to be followed strictly for its smooth operation. Sometimes it becomes difficult to follow this protocol.
- Evaluating the risks involved in the project can shoot up the cost and it may be higher than the cost for building the system.
- There is a requirement for further explanation of the steps involved in the project such as breakthrough, blueprint, checkpoints and standard procedure.
Like This Article?
Follow:

Post Comment | View Comments


