Waterfall Model Advantages and Disadvantages

The original waterfall model, published by Winston W. Royce in 1970, was in fact, not identified by the very name by which we know it today. Royce, in fact, presented the model as a flawed and non-working model. Because of the various advantages that this approach towards software designing and implementation presented, it soon became very popular in the world of software development.

However, before going into the waterfall model's advantages and disadvantages, here is a brief explanation of its working and steps.

The most important aspect of the waterfall model is that unless a particular stage is complete, the next stage cannot be started off with. Here, in this article, we will try to understand a simple waterfall model, broken into six stages. Let us try to understand each of these stages one by one.

Whether you design a small program to add two numbers or you are into developing a software system for the automation of an entire airline company, this is the first stage which can never be overridden. Unless you know what you are going to design, you cannot approach the problem. Here, the specifications of the output or the final product is studied and marked.

With all the requirements and constraints in hand, a final view of how the product should exactly be, is decided. The exact way in which the software should function is mentioned in this stage.

Here the actual work begins. Every type of resource which will be required for the smooth designing of the software, is mentioned here in this phase. What type of database will be required, what type of data should be supported, etc. are some of the important aspects that are decided in this phase.

The algorithm of the process in which the software needs to be designed, is made in this phase. This algorithm forms the backbone for the actual coding process, that takes place in the next phase.

Now starts the coding. Here, the software is coded as per the algorithm. Hence it becomes very important that the algorithm should be properly designed. The software designed, needs to go through constant software testing and error correction processes to find out if there are any flaw or errors.

Here the various codes designed by different programmers are integrated and is tested if the software works as per the specifications provided. The setup of the final software which needs to be installed at the clients system, is also designed and tested, so that the client does not face any problem during the installation of the software. The product is then handed over to the client.

The cycle of software development does not end with handing the software to the client. Software designers may have to constantly provide support to the client to resolve any issues which may arise. During the maintenance phase, support and debugging is provided for all such problems.

» Being a linear model, it is very simple to implement.
» The amount of resources required to implement this model are minimal.
» Documentation is produced at every stage of the software's development. This makes understanding the product designing procedure, simpler.
» After every major stage of software coding, testing is done to check the correct running of the code.

» You cannot go back a step; if the design phase has gone wrong, things can get very complicated in the implementation phase.
» Often, the client is not clear of what he exactly wants from the software. Any changes mentioned in between, may cause a lot of confusion.

» Small changes or errors that arise in the completed software may cause a lot of problems.
» Until the final stage of the development cycle is complete, a working model of the software does not lie in the hands of the client. Thus, he is hardly in a position to inform the developers, if what has been designed is exactly what he had asked for.

So this, in short, was all about waterfall model advantages and disadvantages. In spite of the cons, the many pros of this model ensure that it remains one of the most popular models used in the field of software development.