Tuesday, 4 February 2014



The classical waterfall model is an idealistic one since it assumes that no development error is ever committed by the engineers during any of the life cycle phases. However, in practical development environments,

  the engineers do commit a large number of errors in almost every phase of the life cycle.  The source of the defects can be many:
  •  oversight
  • wrong assumptions
  •  use of inappropriate technology
  • communication gap among the project engineers, etc
. These defects usually get detected much later in the life cycle. For example, a design defect might go unnoticed till we reach the coding or testing phase. Once a defect is detected, the engineers need to go back to the phase where the defect had occurred and redo some of the work done during that phase and the subsequent phases to correct the defect and its effect on the later phases. Therefore, in any practical software development work, it is not possible to strictly follow the classical waterfall model.

1 comment:

  1. Hello,
    The Article on Shortcomings of Waterfall model with Phase is nice, gives detailed information about it. Thanks for Sharing the information about Waterfall Model. For More information check the detail on the Waterfall testing here Software Testing Services

    ReplyDelete