| Waterfall Model | - Easy to understand and implement
- Reinforces good habits: define-before-design and design-before-code.
- Identifies deliverables and milestones
- Works well on mature deliverables
| - Real projects rarely follow sequential approach
- Uncertainty at the beginning of the development
- No working version of the system until very late
|
| Incremental Model | - Divides project into smaller parts
- Creates working model early
- Feedback from one phase provides information for the next phase
- Very useful when more staffing is unavailable
| - Users need to be actively involved in the project.
- Communication and coordination skills are central process
- Informal requests for improvement for each phase may lead to confusion
- It may lead to scope creep
|
| Spiral Model | - Designed to include the best features from Waterfall and Prototyping Model
- Good for large and mission-critical projects
- Introduces risk assessment as a new component
| - Can be a costly model to use
- Risk analysis requires specific expertise
- Project’s success is highly dependent on risk analysis phase
- Doesn’t work well for smaller projects
|
