Software development life cycle
Download as PPTX, PDF0 likes136 views
This document discusses different software development life cycle models including waterfall, prototype, and spiral models. The waterfall model is a linear sequential model that has clear phases but does not allow for much iteration. The prototype model uses iterative development and customer feedback to refine requirements. The spiral model is a combination of iterative and sequential approaches that is useful for medium to high risk projects with uncertain requirements. It allows for risk evaluation and prototyping at each phase.
Software development life cycle
- 2. Introduction âą It specifies the various phases/workflows of the software process, such as the requirements, analysis (specification), design, implementation, and postdelivery maintenance, and the order in which they are to be carried out.
- 3. Choosing Appropriate model âą Increased development speed âą Increased product quality âą Improved tracking & control âą Improved client relations âą Decreased project risk âą Decreased project management overhead
- 4. Common life cycle model âą Waterfall âą Prototype âą Spiral
- 6. Waterfall plus points âą Easy to understand, easy to use âą Provides structure to inexperienced staff âą Milestones are well understood âą Sets requirements stability
- 7. Waterfall weakness âą All requirements must be fully specified upfront âą Can give a false impression of progress âą Does not reflect problem-solving nature of software development â iterations of phases âą Little opportunity for customer to preview the system (until it may be too late)
- 8. Prototype model Design Implement Test Maintain Requirements gathering Quick design Build prototype Refine requirements incorporating Customer suggestion Customer evaluation Of prototype Acceptance By customer Prototype development Iterative development
- 9. Prototype advantages âą Provides a working model to the user early in the process , enabling early assessment and increasing user confidence. âą The developer gains experience and insight by developing a prototype , thereby resulting in better implementation of requirements. âą Helps in reducing risks associated with the project.
- 10. Spiral model Spiral model is an evolutionary software process model which is a combination of an iterative nature of prototyping and systematic aspects of traditional waterfall model.
- 11. When Required ? âą When costs and risk evaluation is important. âą For medium to high-risk projects. âą Users are unsure of their needs. âą Requirements are complex. âą Significant changes are expected.
- 13. pros âą Changing requirements can be accommodated. âą Allows for extensive use of prototypes âą Requirements can be captured more accurately. âą Users see the system early. âą Development can be divided into smaller parts and more risky parts can be developed earlier which helps better risk management.
- 14. cons âą Management is more complex. âą End of project may not be known early. âą Not suitable for small or low risk projects and could be expensive for small projects. âą Process is complex âą Spiral may go indefinitely. âą Large number of intermediate stages requires excessive documentation.