2. Brought to you by:
Courtney Fradreck Taga
(230350)
Dennis U. Ifu (230533)
Presenters
3. Contents of our Presantation.
1. What are software development methodologies?
2. Example: Waterfall, Agile, Scrum, etc.
3. Advantages and Disadvantages of Examples.
4. Visual Presentation of Examples
5. ……………..
5. Storytime
SDLC
SDM
Agile
SDLC
SDLC is a general term that describes the
process of creating software,,
SDM
while software development methodology
is a specific way of implementing the
SDLC.
Agile
There are different types of software
development methodologies, such as
waterfall, agile, scrum, and so on. Each
methodology has its own advantages and
disadvantages, depending on the nature
and scope of the project.
9. What are Software Development Methodoloies
• Software development methodologies are structured approaches to a
software development project that can improve efficiency, quality,
and collaboration.
• They are important because they help developers plan, organize,
execute, and deliver software products that meet the needs and
expectations of the clients and users.
• They also improve efficiency, quality, and collaboration in the software
development process.
10. Overview of Software Developmet Methodologies
1. Waterfall Model
2. Agile Model: Scrum, Kanban, XP
3. Prototyping Model The Spiral Model
4. Rapid Application Development Model
5. Iterative and Incremental Process Model
11. Overview of Software Developmet Methodologies
This is a traditional and linear
methodology that follows a
sequential order of phases, such as
requirements, design,
implementation, testing, and
maintenance. Each phase depends
on the completion and approval of
the previous one. This methodology
is suitable for well-defined and stable
projects, but not for dynamic and
complex ones.
Waterfall Model
12. Pros and Cons of the Waterfall Model.
Simple Structure.
Easy to track resources, time and
cost.
Stable Tasks.
Convenience for developers and
testers.
Pros
Cons
Lacks flexibility.
Rigid framework
Resistance to change
Increased Ricks
15. Agile Model: Scrum, Kanban, XP:
This is a methodology that values flexibility,
collaboration, and customer satisfaction. The agile
model is based on the principles of the Agile
Manifesto, which emphasize adaptive planning,
iterative development, continuous improvement, and
stakeholder involvement. The agile model has several
frameworks, such as Scrum, Kanban, and XP, that
provide specific practices and roles for implementing
the agile principles. The agile model is suitable for
projects that have changing and evolving
requirements and need frequent feedback and
delivery.
16. For more info on Agile, you can
watch the following vidoes
What is Agile? (youtube.com)
Agile vs Waterfall: Choosing Your Methodology –
YouTube
Scrum vs Kanban - What's the Difference? + FREE
CHEAT SHEET (youtube.com)
(1) Agile Cartoons - YouTube
17. OSDM Continued
This is a methodology that combines the
iterative and incremental approach with the risk
analysis and evaluation of the waterfall model.
The software development process is
represented as a spiral, with each loop
consisting of four stages: planning, risk analysis,
engineering, and evaluation. The spiral model is
suitable for large and complex projects that
involve high risks and uncertainties.
Prototyping Model
The Spiral Model
18. OSDM Continued
Rapid Application
Development Model:
This is a methodology that focuses on
delivering software products and
features quickly and efficiently, using
techniques such as prototyping,
timeboxing, and user involvement.
The software development process
consists of four phases: requirements
planning, user design, construction,
and cutover. The rapid application
development model is suitable for
projects that have clear and well-
defined requirements and need fast
delivery.
19. Iterative and Incremental Process Model
Follow the link below to understand more about the methodologies. For more info, click here
This is a methodology that
divides the software development
process into smaller and
manageable iterations, each of
which produces a working version
of the software. The iterations are
repeated until the final product
meets the desired requirements
and quality. This methodology
allows for feedback, changes,
and improvements along the way.