SDLC – Spiral Development Model

SDLC – Spiral Development Model

The Spiral SDLC model is a combination of the Prototyping and Waterfall approaches. It synchronizes well with the natural software development process. The Spiral model features the same phases as Waterfall in the same order (requirements gathering, design, implementation, and testing ), separated by planning, risk assessment, and the building of prototypes and simulations during each step.

Advantages of Spiral development SDLC model:

  • Estimates (budget, schedule, etc.) become more realistic as work progresses since important issues are discovered earlier
  • Early involvement of the development team and users
  • Higher quality of risk management at each phase
  • Better flexibility than in linear models
  • Extended use of prototypes

Disadvantages of Spiral development SDLC model:

  • More money and time required to get the finished product
  • More complicated to execute due to the greater need for risk management
  • Limited reusability due to highly customized results of development spirals
  • Requires heavy documentation

Best for:

  • Complicated projects with a lot of small built-in functionality
  • Projects with strict budgets (risk management will help to save money)
  • High-risk projects
  • Long-term development projects
  • Projects with no clear requirements at the early stages, or with requirements that need to be evaluated
  • New product lines meant to be released in phases
  • Projects where significant changes to the product are likely to occur during development