Software Development : Waterfall Model

What Is Waterfall Model?

The waterfall model is the simplest model in software engineering. This is also called as classic life cycle model. Times when the requirements for a problem are well understood and when work flows from communication through deployment in a reasonably linear fashion. In waterfall model process is carried out in top to down sequentially.   This situation is sometimes encountered when well-defined adaptations or enhancements to an existing system must be made (e.g., an adaptation to accounting software that has been mandated because of changes to government regulations). It may also occur in a limited number of new development efforts, but only when requirements are well defined and reasonably stable.  This model is not used in practice this is only for understanding other model. The waterfall model, sometimes called the classic life cycle, suggests a systematic, sequential approach to software development. We start with the collecting requirements, planning, modelling, construction, and deployment.


Following Phases Occur In Waterfall Model



Communication is the first step before starting any software project.   Before starting any software project it is very important to understand what user wants what user wants from software. Here in this phase we do requirement gathering. We must collect requirement if we have requirements then we can proceed. For example user wants to develop software for theatre management the developer does not know what to do and how it should look like. Then user will provide necessary information to user.



Normally, planning means to draw out in detail what to do in future. Planning is very crucial activity in software engineering. In this phase of development the manager plans for future he decides what problems may occur in future, what are risks involved, budged, cost, schedules etc.



In modelling the engineer designs the architecture of software which is similar to floor plan of house.

The engineer makes detail design of software using requirements collected. You create a “sketch” of the thing so that you’ll understand the big picture



This is also called as implementation here programmer implements the requirements into programming language they code in particular programming languages.



Testing is very important phase basically testing is done to check weather software meets customer requirement or not. In testing we find the problems in our system and remove our problems.

There is lots of testing technique like black box testing, white box testing, top down testing, bottom up testing.



The software (as a complete entity or as a partially completed increment) is delivered to the customer who evaluates the delivered product and provides feedback based on the evaluation.


Software Development


            Problems with Waterfall Model

  • Waterfall model is not being used in industry although it supports iteration but indirectly.
  • If requirements are not stated properly then it leads to bad software product and it can cause confusion as the project team proceeds.
  • There is always uncertainty involved in waterfall model.
  • The customer must have patience.

One team has to depend on another team for example testing team  has to wait till coding team finishes their task. For more reading about technology news in singapore and seo to online marketing do view more about other pages.

Sourabh Bhunje

Sourabh Bhunje, B.E. IT from Pune University. Currently Working at Techliebe. Professional Skills: Programming - Software & Mobile, Web & Graphic Design, Localization, Content Writing, Sub-Titling etc.

Leave a Reply