Waterfall Model

In this topic, you will learn about, the Waterfall Model.

Waterfall Model: the simplest software development model is the waterfall model, which states that the phases are organized in a linear order. There are various variations of the waterfall model depending upon the nature of activities and the flow control between the phases.

In a typical model, a project begins with requirement analysis and specification that is associated with the feasibility study of the project, after the requirements are successfully determined the design phase starts and the coding starts after the design phase. In the coding phase unit testing is also done. Once the programming is completed the code is integrated and testing is done, on the successful completion of the testing, the system is installed.

Waterfall Model
fig: Waterfall Model

Limitation and advantages of Waterfall models:

The waterfall model is the simplest and fastest system, development model. Its phases can be selected and organized according to the project or the developer.

The major limitation of the waterfall model is the requirements are frozen (fixed) before the design begins. And if the requirement specified is incorrect the resulting software of the system will be incorrect.

Another limitation of the waterfall model is its phases are independent that is we cannot move back to any previous phases in this model, for making any kind of changes the process has to be started again from the beginning that is from phase 1 But, the waterfall model is good for small projects where requirements are clearly specified in the beginning.

See also  What is prototyping?