GoConqr hat ein neues Design! Sag uns, wie es dir gefällt.

Flussdiagramm

Methodologies

Javier Alejandro Aranda Ruiz Spanisch

Inhalt des Flussdiagramms

  1. SOFTWARE

    DEVELOPMENT

    METHODOLOGIES

  2. Waterfall

  3. Prototyping

  4. Incremental Build Model

  5. Iterative and Incremental Development

  6. Spiral Model

  7. RAD

  8. Cleanroom

  9. -Sequential design

    process.

    -Progress is seen as

    flowing steadily

    downwards

  10. -Simulates only a few aspects of, and may be completely different from, the final product.

  11. -Combines the elements of the waterfall model with the iterative philosophy of prototyping.

  12. -Any combination of both iterative design or iterative method and incremental build model for development.

  13. -Intended for large, expensive and complicated projects.

    -Advantages of top-down and bottom-up concepts

  14. -Lack of pre-planning generally allows software to be written much faster, and makes it easier to change requirements.

  15. -Embeds software development and testing within a statistical quality control framework.

  16. Agile

  17. Scrum

  18. Lean (Kanban)

  19. Extreme Programming (XP)

  20. DSDM

  21. -Self-organizing, cross-functional teams

    -Adaptive planning,

    -Evolutionary development and delivery,

    -A time-boxed iterative approach,

    •rapid and flexible response to change.

  22. -Development team works as an atomic unit

    -Opposing to sequential approach

  23. 1.Eliminate waste

    2.Amplify learning

    3.Decide as late as possible

    4.Deliver as fast as possible

    5.Empower the team

    6.Build integrity in

    7.See the whole

  24. -Frequent "releases" in short development cycles

    -Introduce checkpoints where new customer requirements can be adopted.

  25. -Fixes cost, quality and time at the outset and uses the MoSCoW prioritization of scope.

    -Must, Should, Could, Would

  26. Test-driven development (TDD)

  27. -Relies on the repetition of a very short development cycle

  28. Rational Unified Process (RUP)

  29. -Adaptable framework, intended to be tailored by the development organizations

  30. V-model

  31. -Show the relationships between development phases and test phases

  32. Dual Vee Model

  33. -Shows interactions and sequences of developing a complex system and a system of systems.

  34. Feature-driven development (FDD)

  35. -Driven from a client-valued functionality (feature) perspective

  36. Javier Alejandro Aranda Ruiz

    ITI10A

Informationen

Beschreibung
Flussdiagramm am Methodologies, erstellt von Javier Alejandro Aranda Ruiz am 19/03/2019.
Aufrufe
0
Bewertung

Feedback

Worum geht es?

Wie gefällt dir das neue Design?

Dein Eindruck