Waterfall Model

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate phases. In Waterfall model, typically, the outcome of one phase acts as the input for the next phase sequentially.

All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.

The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.

With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.

All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.

Once the functional and non functional testing is done, the product is deployed in the customer environment or released into the market.

There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Every software developed is different and requires a suitable SDLC approach to be followed based on the internal and external factors. Some situations where the use of Waterfall model is most appropriate are:

1) Requirements are very well documented, clear and fixed.

2) Product definition is stable.

3) Technology is understood and is not dynamic.

4) There are no ambiguous requirements.

5) Ample resources with required expertise are available to support the product.

6) The project is short.

The waterfall approach is the earliest approach that was used for software development. Initially, most projects followed the waterfall approach because they did not focus on changing requirements.

1) In development of database-related software, eg commercial projects.

2) In development of E-commerce website or portal.

3) In Development of network protocol software.

1) This model is used only when the requirements are very well known, clear and fixed.

2) Product definition is stable.

3) Technology is understood.

4) There are no ambiguous requirements

5) Ample resources with required expertise are available freely

6) The project is short.