Process
Characteristics Suitability Remark
Model
Sequential, documentation-driven, Well-defined, stable Easy to manage but
Waterfall each phase completed before next; requirements; inflexible; no early working
feedback loops small/medium projects software
Complex/unknown Costly and time-consuming;
Build prototype first; users give
Prototyping requirements; large minimal documentation;
feedback; clarifies requirements
innovative systems several prototype types
System developed in increments;
Large systems needing Early usable software;
Incremental each increment adds features;
early partial delivery requires careful planning
iterative mini-cycles
Build basic version of all features Evolving requirements;
Better testing; requires
Iterative first; refine in cycles; feedback- user-feedback-heavy
customer involvement
driven projects
Risk-driven; iterative cycles: Complex and costly;
High-risk, large, expensive
Spiral planning → risk analysis → requires risk analysis
projects
development → evaluation expertise
Fast development; heavy Projects with clear, stable Needs skilled developers
RAD prototyping; short cycles; high user requirements; time-critical and active users; not good
involvement work for very large systems
Fixed time frames; parallel teams; Projects needing fast Not suitable if tasks can't be
Timebox stages of equal duration; delivery with many evenly divided; manpower-
overlapping iterations features intensive
Extension of waterfall; Well-defined, fixed
Rigid; no room for changing
V-Model verification/validation at each requirements; small stable
requirements
phase; strict sequence projects
Short iterations; incremental; Changing requirements; Requires frequent customer
Agile customer-driven; adaptive; fast-moving or dynamic involvement; flexible but
emphasis on working software projects less predictable