Web Development Methodology with Spiral, Methodology for Web Design Development using Spiral Model

Spiral Model

The Spiral Model is a Software Development Process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. It is a meta-model, a model that can be used by other models. Spiral Model of development combines the features of the prototyping and the waterfall model. The spiral model is intended for large, expensive and complicated projects. The Spiral Model combines the idea of Iterative Development (prototyping) with the systematic, controlled aspects of the Waterfall Model. It allows for incremental releases of the product, or incremental refinement through each time around the spiral. The Spiral Model also explicitly includes risk management within software development. Identifying major risks, both technical and managerial, and determining how to lessen the risk helps keep the software development process under control. The Spiral Model is based on continuous refinement of key products for requirements definition and analysis, system and software design, and implementation  (the code). At each iteration around the cycle, the products are extensions of an earlier product. This model uses many of the same phases as the waterfall model, in essentially the same order, separated by planning, risk assessment, and the building of prototypes and simulations. Starting at the center, each turn around the spiral goes through several task regions,

1. Determine the objectives, alternatives, and constraints on the new iteration.
2. Evaluate alternatives and identify and resolve risk issues.
3. Develop and verify the product for this iteration.
4. Plan the next iteration.

The requirements activity takes place in multiple sections and in multiple iterations, just as planning and risk analysis occur in multiple places. Final design, implementation, integration, and test occur in iteration 4. The spiral can be repeated multiple times for multiple builds. Using this method of development, some functionality can be delivered to the user faster than the waterfall method. The spiral method also helps manage risk and uncertainty by allowing multiple decision points and by explicitly admitting that all of anything cannot be known before the subsequent activity starts.