Waterfall and spiral model

  • Published on

  • View

  • Download

Embed Size (px)




  • 1. Reported by: Honey Mae Llanto

2. It is a model which wasdeveloped for softwaredevelopment; that is to createsoftware. This was first put forthby Winston Royce in 1970 in one ofhis articles. 3. Analysis Design Technical Design/ Detailed Design Implementation and Coding Testing Integration Acceptance Test Management and Maintenance 4. The project requires the fulfillment of onephase, before proceeding to the next. Provides structure to inexperienced staff Works well when quality is more importantthan cost or schedule 5. Many software projects are dependent uponexternal factors. A huge amount of time is also wasted. Little opportunity for customer to previewthe system. All requirements must be known upfront 6. Requirements are very well known Product definition is stable Technology is understood New version of an existing product 7. This model is preferred for large, expensiveand complicated projects. It combines thefeatures of Prototyping and Waterfallmodels. 8. Envisioning Phase Planning Phase Developing Phase Stabilizing Phase Deploying Phase 9. Early and frequent feedback from users Users see the system early because of rapidprototyping tools Provides early indication of risks. Users can be closely tied to all lifecyclesteps 10. Time spent for evaluating risks too large The model is complex Risk assessment expertise is required May be hard to define objective, verifiablemilestones that indicate readiness toproceed through the next iteration 11. When creation of a prototype isappropriate Requirements are complex Significant changes are expected Users are unsure of their needs 12. End ^-_^