WATERFALL MODEL IN SYSTEM DEVELOPMENT

LIFE CYCLE (SDLC)

The waterfall model of the software life cycle which 1st put forward by Royce in 1979. It become popular in the 1970s. However, when Boehm brought attention to it. there are many variants of the waterfall model depending on the organization the use the model and the specific projects.

Presentation by Management Study Online (MSO)

FIG 1: LINEAR-SEQUENTIAL WATERFALL MODEL

The Above figure depicts Linear-Sequential Waterfall model. 

Another variant of the waterfall model is the one in which each phase's results flow into the next and the process. Ideally process in an orderly fashion. this can be illustrated from the next figure. 

FIG 2 : WATERFALL MODEL

In the waterfall model "With feedback the process is structured as a cascade of phases where the output of one phase constitute the input to the next one. The Waterfall model consist of the Following Phases.

1. FEASIBILITY STUDY Feasibility study is study about finding out the

Problems. in this phase feasibility is an evaluation and analysis of the potential of proposed which is based on extensive investigation and research to support to process in decision making.  

AimsWork out on overall understanding of the problems.Generate Different Solution for solving the Problem.Find out the Solution among alternative which is suitable

and best.Analysis each and every alternatives solution in terms of :

What are the Resources RequiredWhat are the Cost of DevelopmentHow much time taken in development etc

2. REQUIREMENT ANALYSIS AND SPECIFICATION In this phase Developer understand

the exact requirements of the customers.  after the knowing requirement of the customers. developer need to gathering information and analysis it. 

AimsRequirement gathering and analysisAnalysis the collected data.. is

relevant or notRequirement specificationFind out if any requirement is not

completed. and solve it.

3. DESIGN AND SPECIFICATION In this design phase developer transform

the Gathered requirement specification data into a particular format and bring it in a structure format. 

AimsDesign phase transforms requirement

specification data into a Programming language structure.

Bring all gathered customers requirement in a particular format for developing the software.

4. CODING AND MODULE TESTING In this Phase developer

start developing this software. now in this phase developer start coding using programming language according to the requirement of the customers.

AimsConvert software design into source

code.Dividing in module if software have

many function.Testing each module after the

coding. if developer test individual module is working correctly or not.

Integration and System testing In this phase After the developing every

module and its testing developer integrate all module and made one software/system. "For example: developer divided one software into 4 module and after the developing of module 1, 2, 3, and 4 developer integrate all module each other and developed one software" after the integration he test whole software and test each and every functions of the software.

Aims Integrate all module in a system. Ensure that the developed system functions

working according to the requirement of the customers as specified in the document.