+Software development methodologies
2 likes984 views
This document discusses and compares various software development methodologies. It describes the Waterfall model, Prototyping model, Incremental model, Iterative model, Spiral model, RUP, XP, Agile, Scrum, Lean, DSDM, RAD and FDD methodologies. It explains that a methodology provides a formalized or systematic process for creating software. Methodologies can be sequential like Waterfall or iterative like Agile approaches. The document also gives overviews of specific methodologies like Scrum, Lean, XP and DSDM.
+Software development methodologies
- 2. Methodologies • Waterfall • Prototype model • Incremental • Iterative • DSDM • RUP • XP • Agile 2Walid Sassi • Iterative • V-Model • Spiral • Scrum • Cleanroom • RAD • Agile • Lean • Dual Vee Model • TDD • FDD
- 3. Definition • A methodology is a formalized process or set of practices for creating software • A set of rules you have to follow 3Walid Sassi • A set of conventions the organization decides to follow • A systematical, engineering approach for organizing software projects
- 4. Waterfall 4Walid Sassi • Sequential design process • Progress is seen as flowing steadily downwards (like a waterfall) through SDLC
- 5. Waterfall • Jump to next phase only if the prior one is completed • PROs • Detailed early analysis cause huge advantages at later phases • If a bug found earlier, it is much cheaper (and more effective) to fix 5Walid Sassi • If a bug found earlier, it is much cheaper (and more effective) to fix than bugs found in a later phase • Requirement should be set before design starts • Points to importance of documentation (minimized “broken leg” issue) • Disciplined and well-structured approach • Effective for stable software projects • Easy to plan from project management point of view
- 6. Waterfall • CONs • Changes are expensive • Client does not explicitly know what he or she wants • Client does not explicitly know what is possible to have • Need to finish every phase fully 6Walid Sassi • Need to finish every phase fully • Long projects, difficult to keep the plan • Designers may not know in advance how complex a feature’s implementation • “Measure twice, cut once”
- 7. Prototyping • Creating prototypes of software applications i.e. incomplete versions of the software program being developed 7Walid Sassi • A prototype typically simulates only a few aspects of, and may be completely different from, the final product.
- 8. Incremental Build Model • The model is designed, implemented and tested incrementally (a little more is added each time). • Finished when satisfies all the requirements. • Combines the elements of the waterfall model with 8Walid Sassi • Combines the elements of the waterfall model with the iterative philosophy of prototyping.
- 9. Iterative and Incremental Development • Iterative and incremental development is any combination of both 9Walid Sassi iterative design or iterative method and incremental build model for development.
- 10. Incremental vs. Iterative 10Walid Sassi
- 11. Effort in Iterative Development 11Walid Sassi
- 12. Spiral Model • Combining elements of design and prototyping- in-stages • Combines the features of 12Walid Sassi • Combines the features of the prototyping and the waterfall model • The spiral model is intended for large, expensive and complicated projects.
- 13. RAD (rapid app dev) • Minimal planning and fast prototyping. • Developing instead of planning 13Walid Sassi planning • The lack of pre-planning generally allows software to be written much faster, and makes it easier to change requirements.
- 14. Agile • Group of software development methods • Based on iterative and incremental development • Most important phrases • self-organizing, cross-functional 14Walid Sassi • self-organizing, cross-functional teams • adaptive planning, • evolutionary development and delivery, • a time-boxed iterative approach, • rapid and flexible response to change. • A conceptual framework • The Agile Manifesto in 2001.
- 15. Agile Manifesto 2001 “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software” 15Walid Sassi software”
- 16. Scrum • Scrum is an iterative and incremental agile software development framework • A flexible, holistic 16Walid Sassi • A flexible, holistic product development strategy • Development team works as an atomic unit • Opposing to sequential approach
- 17. Lean (Kanban) • A translation of lean manufacturing principles and practices 17Walid Sassi • Toyota Production System, • Today part of Agile community.
- 18. Lean Principles 1. Eliminate waste 2. Amplify learning 3. Decide as late as possible 18Walid Sassi possible 4. Deliver as fast as possible 5. Empower the team 6. Build integrity in 7. See the whole
- 19. Extreme Programming (XP) • Improve software quality and responsiveness to changing customer requirements • A type of agile software development 19Walid Sassi development • Frequent "releases" in short development cycles • Introduce checkpoints where new customer requirements can be adopted.
- 20. XP Concepts • Pair programming • Planning game • Test-driven development 20Walid Sassi development • Continuous integration
- 21. DSDM • An agile project delivery framework, primarily • DSDM fixes cost, • M - MUST: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success. • S - SHOULD: Represents a high- priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary. 21Walid Sassi • DSDM fixes cost, quality and time at the outset ways if strictly necessary. • C - COULD: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit. • W - WOULD: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.