SDLC Models and

Methodologies
By: Nino Herrera
Feature
Waterfall Model

Approach
Linear, sequential
Flexibility Low

Risk Management High (risks identified

early, but hard to
change)

Development Speed
Slow

Iteration Type None (one-time

process)

Requirements →
Phases Design →
Implementation →
Testing →
Deployment

Cost Efficiency Can be costly if

changes are required
late

Best For
Stable projects with
clear requirements
User Feedback
Integration Late in the process

Project Suitability
Fixed, well-defined
requirements
Spiral model

Feature
Spiral Model

Approach
Cyclic, risk-driven
Flexibility Moderate

Risk Management
Strong focus
Development
Speed Moderate

Iteration Type
Large cycles

Phases
Plan → Risk → Dev
→ Eval (Repeat)

Cost Efficiency
Expensive due to risk
management

Best For
High-risk, long-term
projects
User Feedback
Integration Each cycle

Project Suitability
High-risk industries
Feature
Hybrid Model

Approach
Mix of models
Flexibility High

Risk
Management
Varies
Development
Speed Varies

Iteration Type
Depends

Phases

Mixed

Cost Efficiency
Varies

Best For
Flexible projects
User Feedback
Integration Varies

Project
Suitability
Customizable needs
Iterative
Feature Iterative Model
Repetitive
Approach improvement
Flexibility Very High

Risk
Management Moderate
Development
Speed Fast

Iteration Type Continuous

Phases Small cycles

Cost Efficiency Cost-effective

Best For Evolving projects

User Feedback
Integration Continuous

Project
Suitability Startups, Agile
Incremental
Feature Incremental Model
Build in functional
Approach increments
Flexibility Moderate

Lower due to early

Risk Management delivery

Development Speed Moderate

Iteration Type Stepwise increments

Planning →
Increment Dev →
Phases Testing

Efficient for large

Cost Efficiency projects

Large projects with

Best For clear phases
User Feedback
Integration After each increment

Medium to large
Project Suitability apps
Feature Prototyping Model
Quick prototype
Approach before full dev
Flexibility High

Risk Identifies early but

Management overlooks long-term
Development Fast early, slower
Speed later
Early prototype, then
Iteration Type refine

Prototype → User
Feedback → Final
Phases Dev

Reduces cost early,

Cost Efficiency may increase later

Best For User-centric projects

User Feedback
Integration Heavy in early phases

Project
Suitability UI-heavy apps
 Feature V-Model
Sequential, parallel
Approach testing
Feature V-Model
Flexibility Low
Sequential, parallel
Approach testing
Flexibility Low
Risk Management Strong, strict testing

Development Speed Slower

Risk Management Strong, strict testing

Iteration Type No iteration

Development Speed Slower

Iteration Type No iteration

Analysis → Design →
Phases Coding → Testing

Analysis → Design →
Phases Coding → Testing
Cost Efficiency Expensive

Cost Efficiency Expensive

Best For Critical systems
User Feedback
Integration Final testing only
Best For Critical systems
User Feedback
Integration Final testing only
Project Suitability Safety-critical

Project Suitability Safety-critical

Rapid application development
(RAD) model
Feature RAD

Approach Rapid prototyping

Flexibility Very High

Risk Management Moderate

Development Speed Very Fast

Iteration Type Continuous

Business → Data →
Phases Process → Dev

Cost-effective for
small-medium
Cost Efficiency projects

Best For Fast-delivery projects

User Feedback
Integration Continuous

Rapid apps needing

Project Suitability fast time-to-market
Agile
Feature Agile

Approach Iterative, flexible

Flexibility Extremely High

Continuous
Risk Management assessment
Development
Speed Very Fast

Iteration Type Time-boxed sprints

Concept → Sprint
Phases Planning → Dev

Cost-efficient due to
Cost Efficiency minimal rework

Changing
Best For requirements
User Feedback
Integration Core principle

Dynamic, evolving
Project Suitability projects
Agile-
Agile- Extreme programming
XP (Extreme
Feature Programming)
Agile with strong
Approach coding practices
Flexibility High

Managed through
Risk Management test-driven dev

Development Speed Fast

Frequent small
Iteration Type releases

Planning → Coding
Phases → Testing → Release

Costly (requires high

Cost Efficiency discipline)

Best For High-discipline teams

User Feedback
Integration Core principle

Strict Agile teams

Project Suitability with rapid iterations
Agile- Crystal methods
Feature Crystal Methods
Lightweight Agile
Approach framework
Flexibility High

Risk
Management Adaptable
Development
Speed Fast

Iteration Type Customizable

Phases Discovery → Delivery

Cost-effective for
Cost Efficiency adaptive teams

Small, adaptable
Best For teams
User Feedback Feature-driven
Integration feedback

Project Small teams needing

Suitability adaptability
Agile- Feature driven development
FDD (Feature-Driven
Feature Development)

Approach Feature-based Agile

Flexibility High

Moderate (features
Risk Management prioritized)
Development
Speed Fast

Iteration Type Feature-driven cycles

Feature → Plan →
Phases Design → Dev

Costly if feature
Cost Efficiency scope is large

Feature-heavy
Best For projects
User Feedback
Integration Ongoing

Feature-rich software
Project Suitability dev
Agile- Scrum
Feature Scrum

Approach Sprint-based Agile

Flexibility High

Risk Moderate (backlog

Management management)
Development
Speed Sprint-based

Iteration Type 1-4 week sprints

Backlog → Sprint
Planning →
Phases Execution

Cost Efficiency Moderate

Best For Sprint-driven teams

User Feedback Based on criteria
Integration weighting

Project Teams needing

Suitability structured sprints
SCHEDULING AND DECISION
TOOLS
 Gantt Charts

•A Gantt chart provides a graphical illustration of a schedule that helps to plan, coordinate and track specific tasks in a project,
•The horizontal axis of the Gantt chart is a time scale, expressed either in absolute time or in relative time referenced to the
beginning of the project.
Agile- kanban
Kanban
Continuous
workflow
High

Low (flow-based)
Continuous
Continuous

Prioritize →
Develop → Deploy

Moderate
Lean teams with
constant flow
After sprints
Process-heavy
teams
 Decision Support Matrix
Decision Support Matrix is not a type of SDLC but rather a decision making tool, A decision support matrix, often simply called a decision matrix, is a tool that helps you make informed decisions
by systematically evaluating and comparing different options.
Here's a breakdown of what it is and how it works:

Core Concept: Decision Support Matrix (DSM)

It's a structured framework, typically in the form of a table, that allows you to weigh various options against a set of relevant criteria.
Structured decision-making based
It provides a clear, visual representation of your choices, making it easier to analyze and compare them. on criteria evaluation
It aims to reduce subjectivity and bias in decision-making by introducing a more objective, quantitative approach.
Depends on criteria & weights
Systematic (evaluates risks per
option)
Depends on criteria complexity
No iteration, but evaluates options
systematically

Define → Evaluate → Rank →

Decide

Depends on alternatives analyzed

Decision-making scenarios

Strategic planning & choices

 In summary
FDD (Feature-
Waterfall Spiral Model Hybrid Model Iterative Model Incremental Prototyping V-Model RAD Agile XP (Extreme Crystal Methods Driven Scrum
Model Model Model Programming)
Development)
Feature

Build in
Linear, Repetitive functional Quick prototype Sequential, Rapid Agile with strong Lightweight Agile Feature-based Sprint-based
Approach sequential Cyclic, risk-driven Mix of models improvement increments before full dev parallel testing prototyping Iterative, flexible coding practices framework Agile Agile

Flexibility Low Moderate High Very High Moderate High Low Very High Extremely High High High High High
High (risks
identified
early, but Identifies early Managed Moderate Moderate
Risk hard to Lower due to but overlooks Strong, strict Continuous through test- (features (backlog
Management change) Strong focus Varies Moderate early delivery long-term testing Moderate assessment driven dev Adaptable prioritized) management)

Development Fast early, slower

Speed Slow Moderate Varies Fast Moderate later Slower Very Fast Very Fast Fast Fast Fast Sprint-based

None (one- Stepwise Early prototype, Time-boxed Frequent small Feature-driven

Iteration Type time process) Large cycles Depends Continuous increments then refine No iteration Continuous sprints releases Customizable cycles 1-4 week sprints

Requirements
→ Design →
Implementati
on → Testing Planning → Prototype → Analysis → Planning → Backlog → Sprint
→ Plan → Risk → Dev Increment Dev → User Feedback → Design → Coding Business → Data Concept → Sprint Coding → Testing Discovery → Feature → Plan Planning →
Phases Deployment → Eval (Repeat) Mixed Small cycles Testing Final Dev → Testing → Process → Dev Planning → Dev → Release Delivery → Design → Dev Execution

Can be costly Reduces cost Cost-effective for Cost-efficient due

if changes are Expensive due to risk Efficient for large early, may small-medium to minimal Costly (requires Cost-effective for Costly if feature
Cost Efficiency required late management Varies Cost-effective projects increase later Expensive projects rework high discipline) adaptive teams scope is large Moderate
Stable
projects with
clear High-risk, long-term Large projects User-centric Fast-delivery Changing High-discipline Small, adaptable Feature-heavy Sprint-driven
Best For requirements projects Flexible projects Evolving projects with clear phases projects Critical systems projects requirements teams teams projects teams

User Feedback Late in the After each Heavy in early Feature-driven Based on criteria
Integration process Each cycle Varies Continuous increment phases Final testing only Continuous Core principle Core principle feedback Ongoing weighting

Fixed, well- Rapid apps Strict Agile teams Small teams

defined Customizable Medium to large needing fast Dynamic, with rapid needing Feature-rich Teams needing
Project Suitability requirements High-risk industries needs Startups, Agile apps UI-heavy apps Safety-critical time-to-market evolving projects iterations adaptability software dev structured sprints