Skip to content
Knowledge Base
Software Engineering
Software Process
Software Processes Model
Comparison And Conclusion

Comparison And Conclusion

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