Spiral Model

1.       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. 2.       Adaptability in the design of spiral model in software engineering accommodates any number of changes that may happen, during any phase of the project. 3.       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. 4.       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.

1.       Spiral models work best for large projects only, where the costs involved are much higher and system pre requisites involves higher level of complexity. 2.       Spiral model needs extensive skill in evaluating uncertainties or risks associated with the project and their abatement. 3.       Spiral models work on a protocol, which needs to be followed strictly for its smooth operation. Sometimes it becomes difficult to follow this protocol. 4.       Evaluating the risks involved in the project can shoot up the cost and it may be higher than the cost for building the system. 5.       There is a requirement for further explanation of the steps involved in the project such as breakthrough, blueprint, checkpoints and standard procedure.