Spiral model
lastmod 2015-03-04created 2015-03-041 edits
The spiral model is one of the classic software development methodologies. It is called the spiral model because it iterates while drawing a spiral shape. The first person to propose the spiral model theory was Barry W. Boehm.
In the spiral model, software is developed in the following stages.
- Requirements and risk analysis
- Planning and architect iteration
- Implementation
- Testing and verification
Detail
The key point is to identify risk factors before each iteration and eliminate them in advance. In the spiral model, every time the next iteration proceeds, the parts with the highest risk in terms of functionality and performance are handled and eliminated first. In other words, the keyword is never to postpone the riskiest parts, or the aspects most prone to bugs, until the last stage of development.
The first advantage of iterative development is that the client can see at least a prototype in advance, even if it is not the finished project. Through this, communication with development, that is, feedback, becomes possible. Also, to maximize the benefits of iteration, iterations should be performed frequently. The reason is that if a problem occurs during an iterative development stage, it is most likely in the most recently changed or added work. Therefore, frequent iterations make it easy to find where things went wrong, reducing the time wasted on bugs.