• Most generic of the models. Most life cycle models can be derived as special cases of the spiral model • Set of important requirements are selected for each prototype. Thus, developers can split the requirements and work first on those with high priority • Employs a risk management approach to software development especially in the stages of Specification, Design, Implementation and Integration • Emphasizes the need to reiterate earlier stages a number of time as the project progresses • Actually a series of short waterfall cycles, each producing an early prototype, representing a part of the entire project. It’s like using the waterfall model as guide in doing one prototype only. • If one prototype is finished (except perhaps the polishing of graphics), a developer can proceed to the next prototype. Build, test and integrate to the first prototype • Helps demonstrate a proof of concept early in the cycle • Incorporates prototyping and software quality objectives • Gives early focus to reusable software • Accommodates life cycle evolution, growth and requirement changes • Focus on early detection and design (architecture) flaws • Useful in hardware-software projects
"Spiral Model"
No comments yet. -