Waterfall

o
o
o

Oldest model and understood by upper management

Plan driven
When to use
o Small scale project
o Requirement well understood and risk is low
o Only allow few changed
Disadvantages
o Difficult response change
o Doesnt support iteration
o Difficult ask customer state all requirement explicit
o Required customer patient
o Have to wait previous stage to start new stage

Prototype
o
o
o
o

Requirement not well understood

Mechanism identify software requirement
Software aspect visible to customer and user
Feedback is used to refine

Spiral
o
o
o
o
o
o

Requirement not well understood and high risk

Inner focus software requirement and project risk
Outer take on waterfall approach, but allow iterative growth
Risk driven model therefore required risk expertise
Combination of plan driven and agile model
Large scale software development

Incremental
o
o
o

Hybrid combine waterfall and evolutionary

Specification, design and implementation broke to small phase
Advantages
o Process iteration
o Reduce rework
o Decision requirement can delay
o Early deliver
o Risk driven
o Easier integration

Disadvantages
o
o
o

Increment need to be small

Mapping requirement to increment it is not easy
Common software facilities may difficult to identify