WATERFALL MODEL

The Waterfall Model Is Useful but Flawed

Abstract

The famous Waterfall Model is the oldest approach being followed in software designing. This approach requires strict following of the sequence of steps. Software being developed on large scales requires reconfiguration and reconsiderations of the requirements and specifications during designing. They may also require up gradation at certain levels. In such scenarios the credibility of the famous waterfall becomes doubtful. This paper aims at discussing the advantages, disadvantages and reformations of waterfall model in detail.

The Waterfall Model Is Useful but Flawed

Introduction

The waterfall model is an approach in the software development process. This model offers a sequential approach in establishing the flow of the software. It is also called a linear sequential model. This is the simplest and generally used approach in software designing. In waterfall model the sequence of the steps in which the software will be developed, is the key. It is necessary that each and every step is properly carried out and then move onto the next step. The waterfall model does not allow switching between the steps during the entire process. This is not an iterative model as going back to the previous step, if once completed is not possible.

In 1970, Winston W. Royce stated that the waterfall model is inflexible and rigid. He tried to modify the model introducing the feature of iteration. Still this model is widely used as it is in software engineering for the development of software. Cascaded mode is followed using this model. The next step is only pursued when the goals of previous step are achieved.

Flow of Waterfall Model

As the name implies, the flow of the model ascends step wise in a downward manner, like a waterfall. The waterfall model is generally follows five sequential phases. These phases are elaborated in detail to get a clear understanding about the Waterfall Model

Requirements and Specifications Analysis

The first step is the identification of the specifications required for the software. These are identified according to the specifications provided by the customer. To meet the specifications of the customer the requirements are set that forms a final product. It is also important to make sure that the separate domains in the system are properly integrated. The decisions related to system working manners are made in this phase. When all the requirements are identified a document containing the details is generated.

Design Flow

This is the main step of all because in this the design of the system is made. All the equipments and resources that will be used are identified. All the algorithms and databases that will be used in the software are created. After the basic draft gets approved, the technical flow of the system is being designed. It is concerned engineering and programming modules that are needed to meet the requirements of the customer.

Implementation

In this step the algorithms and databases that were designed in previous step are implemented as per requirements. For the designed modules, programming is being done. The phase is very delicate and complex and ...