Waterfall model in SDLC

Waterfall Model in SDLC

A software development process or life cycle is astructure imposed on the development of a softwareproduct. There are several models for such processes,each describing approaches to a variety of tasks oractivities that take place during the process.

www.hndassignments.co.uk

• Waterfall model

• V model

• Incremental model

• RAD model

• Agile model

• Iterative model

• Spiral model


There are total 7 models in software development.Waterfall model is a popular model of the systemdevelopment life cycle. It is very simple to use andunderstand. In a waterfall model, each phase must becompleted before the next phase can begin and there isno overlapping in the phases.



• Requirements: Requirements is the initial step inwaterfall model. All possible requirements of thesystem to be developed are captured in this phaseand documented in a requirement specificationdocument. In this steps user demands the entirerequirement for the software development.


• Design: This is the second step in waterfall model.This system design helps in specifying hardware andsystem requirements and helps in defining the

overall system architecture.


• Implementation: It is very important part ofwaterfall model. After requirements and design thenext step in implementation. With inputs from thesystem design, the system is first developed in smallprograms called units, which are integrated in thenext phase. Each unit is developed and tested for itsfunctionality, which is referred to as Unit Testing. Themain purpose of these steps is to execute theprogram.


• Verification: In these steps the entire systems willbe tested for any faults and failures. Once thefunctional and non-functional testing is done theproduct is deployed in the customer environment orreleased into the market.


• Maintenance: In these last steps there are someissues which come up in the client environment. Inthis steps the issue will be fixed, patches arereleased. Maintenance is done to deliver thesechanges in the customer environment.


• This model is simple and easy to understand and use.

• It is easy to manage due to the rigidity of the model –each phase has specific deliverables and a review process.

• In this model phases are processed and completed one at a time. Phases do not overlap.

• Waterfall model works well for smaller projects where requirements are very well understood


• Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.

• No working software is produced until late during the life cycle.

• High amounts of risk and uncertainty.

• Not a good model for complex and object-oriented projects.


• Poor model for long and ongoing projects.

• Not suitable for the projects where requirements are at a moderate to high risk of changing.


• This model is used only when the requirements are very well known, clear and fixed. Product definition is stable.

• Technology is understood.

• There are no ambiguous requirements

• Ample resources with required expertise are available freely

• The project is short.


Visit us for help

Like us on Facebook

Tweet us

Education

Waterfall model in SDLC