1. Estimates (i.e. budget, schedule, etc.) become more realistic as work progresses, because important issues are discovered earlier.
2. It is more able to cope with the (nearly inevitable) changes that software development generally entails.
3. Software engineers (who can get restless with protracted design processes) can get their hands in and start working on a project earlier.
Chat with our AI personalities
spiral model is iterative model hence its easy to implement it .
The spiral model is called a meta model since it encloses all other life cycle model.
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
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 .
There are many differences exists between waterfall model and spiral model. In waterfall model if any sudden change takes place in the project, then its very hard to fix the issue. Wherein spiral model we can change according to our requirement.