Comparison between Prototyping and Waterfall

Similarities

 

Dissimilarities

Waterfall Model

Prototype Model

  • Client can only preview the system only after the final version of the software is developed because there is no feed back loop.
  • Client have a preview of the system from the "quick design" and the prototype developed early at the of the process.
  • Developers encounter a freezing requirement where they are not allow to modify the requirements or specification of the previous phase until the next iteration.
  • Developers can refine or add requirements and specification to the system after the prototype is built.
  • The complexity of an error increases because of the nature of the model; each phase is sequential of the other.
  • The complexity of an error is low because the prototype enables the developer to detect any deficiency early at the process.