we use this model when user is not sure of project need.....when risk and cost evaluation is important for project .........and when project has complex requirement or new product line is introduce...
The win-win spiral approach is very similar to the spiral model in that it is simply an extension of the spiral model. In the win-win model approach, everyone discusses things together to figure out what should go into the new version of the software.
Spiral model was developed by Dr. Barry Boehm . This model was mainly used to evaluate and resolve risks in the software project.
Spiral Model.........
Select a Software Project TITLE
In spiral model the main emphasis is on the management to evaluate and resolve risks in the software project. There is no maintenance phase in spiral model because instead risk is evaluated .
Select a Software Project TITLE
prototype model is suitable when user requirement are not very clear, while spiral model suitable for large projects whether customer requirement are not known in the beginning
The evolutionary software process model involves working with the customers. It starts by specifying clear requirements of the software and features suggested by the customer are added later during development.
The spiral model thus may suit small (up to $3 million) software applications and not a complicated ($3 billion) distributed, interoperable, system of systems.
The spiral model is used by reputable companies such as IBM, Microsoft, Patni Computers and Tata Consultancy where large projects are involved.
The waterfall model is a linear model that follows a sequence as activities move from one to another. The spiral model is a circular model that breaks software development into smaller segments.
Not all models of software engineering are risky. The spiral model takes care of risk in every phase.