The Spiral model

What is it? The spiral model is a system development lifecycle model. It combines the prototyping model and the waterfall model. It allows refinement throughout each stage of the model. This means that one stage can be skipped for testing and returned to at a later point.

The design:

The Design: This model has four main phases: Identification: The analyst gathers information about the requirements and starts to understand what needs to be done. They are in constant contact with the client. Design: The design stage involves architectural design, logical design, physical design and final design. Construction or build: The construction phase occurs at every spiral. The product will be built at least three times due to testing and improvements. Evaluation or risk analysis: Evaluation takes place in every spiral. This means that the product and process will be continually tested for feasibility.

When is best to use it? Many reasons to use the spiral method are listed below: For high-risk projects The client is not sure about what requirements they want When the new product needs customer feedback to improve it Significant/major changes

Benefits & drawbacks: Benefits Drawbacks Allows the use prototyping Management is more complex Client can see the system early on Should not be used for small projects Changes in requirements can be made easily This method requires a lot of documentation

Recap video: Preview not availableSpiral Process - Georgia Tech - Software Development ProcessWatch on Udacity: https://www.udacity.com/course/viewer#!/c-ud805/l- 1719379003/m-547028656 Check out the full Advanced Operating Systems course for free at: ...196 views·22/02/2015YouTube/Udacity

The End