Showing posts with label ƒClassical Waterfall Model. Show all posts
Showing posts with label ƒClassical Waterfall Model. Show all posts

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

 phase of the life cycle of waterfall model


 feasibility study: -  

The main aim of feasibility study is to determine whether it would be financially and technically feasible to develop the product.

ƒ     At first project managers or team leaders try to have a rough understanding of what is required to be done by visiting the client side. They study different input data to the system and output data to be produced by the system.

Monday, 3 February 2014

Different phases of the classical waterfall model


The classical waterfall model is intuitively the most obvious way to develop software. Though the classical waterfall model is elegant and intuitively obvious, it is not a practical model in the sense that it can not be used in actual software development projects. Thus, this model can be considered to be a theoretical way of developing software. But all other life cycle models are essentially derived from the classical waterfall model.

Different software life cycle models


Many life cycle models have been proposed so far. Each of them has some advantages as well as some disadvantages. A few important and commonly used life cycle models are as follows:

  • ƒClassical Waterfall Model
  • ƒIterative Waterfall Model