---
Video Title: Waterfall Model
Description: Waterfall Model
Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm
Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited
---

In our software
development paradigm, we are going to

discuss a very
famous method that is our waterfall model.

So, using this strategy, we can develop
our softwares.

In our discussion, we shall discuss what
is the waterfall model, what are the

merits and demerits, and when to use
waterfall model.

So, whatever model is the simplest model
of software development paradigm and all

the phases of SDLC will function one after
another in a linear and sequential fashion

or manner.

That is when the first
phase is finished, then

only the second phase
will start and so on.

In this way, the phase wise, the respective
software development will be done.

So, here we have considered some of the
phases.

So, recommend gathering, system analysis,
then going for coding, then testing,

then implementation, then operations and
maintenance.

So, in this way, we have gone through.

In our earlier video, in our software
development paradigm, we have discussed

all these respective phases, what are
their purposes,

and what are
the main objective in each and every phase.

You can watch that video also.

So, this model assumes that everything is
carried out and taken place perfectly as

planned in the previous stage.

And there is no need to think about the past
issues that may arise in the next phase.

So, that means, we
know that when water falls, then from

the higher level
to the next high level, it will be falling.

Then from this high
level to the next high level

or the next lower
level, it will be falling.

But it cannot roll up, but it cannot roll
up.

It cannot roll up.

It can only roll down.

And that is why, whatever the issues we
will be having here, we should fix it,

then we should come to the next phase.

And in this
particular phase, we should not consider

any issue
related with the previous phase or phases.

This model does not work.

This model does not work smoothly if there
are some issues left at the previous step.

The sequential nature
of model does not allow

us to go back and
undo or redo our actions.

So, that is the main feature of this
waterfall model.

This model is best suited when developers
already have the designed and developed

similar softwares in the past and are
aware of all its domains.

When the requirements are known at
front beforehand,

then only this
particular waterfall model can be applied.

And if the developers are having the prior
experience developing the software in the

same domain, then this waterfall model can
be used.

It can be utilized, can be implemented.

Otherwise, you see, you cannot retrace
back.

There is, there
is no scope to going back to the previous

step or phase and
do some rework and do and undo there.

That is not possible.

Now, let us discuss waterfall strengths.

So, in case of waterfall strengths,
the first question is that ease of use,

easy or difficult.

The answer is easy to understand and easy
to use and provides structure what is the

future to the other.

To ensure that the future to experience
staff.

For the freshers in the project
management, the software developing

projects, this waterfall model is
suitable.

Clarity or milestones, clear or not answer
is well understood.

Milestones will segregate between one
phase to another phase.

So, whenever we are crossing one milestone
that means, we cannot revert back,

we cannot retrace our path again.

So, in our project management,
this milestone will be denoted by an.

Activity with the duration 0, but here
actually this milestone is denoting that

differentiation or the segregation between
two adjacent consecutive phases.

So, importance is given to quality or on
schedule.

The answer is works well when the quality
is more important than cost or schedule.

So, this is these are the strengths of
waterfall model.

So, now, let us go for the waterfall
deficiencies.

Can new requirements be taken into
consideration during the development phase?

So, when the when the software is getting
developed, can it incorporate the new

change requests, new requirements?

As it is all requirements must be known
upfront beforehand.

So, when the system is getting
developed, when the software

system is getting
developed, no new change requests.

Can deliverables be subjected to change?

Answer is,
deliverables created for each phase

are considered frozen
and inhibits flexibility.

Next one is, can the customer preview the
system during the development phase?

So, can customer see that how far the
software has got developed?

Can the customer have the continuous
participation in the development process?

Answer is, little opportunity for
customers to preview the system until it

may be too late.

So, these are the different deficiencies
are there in our waterfall model.

Now, the question is that when to use the
waterfall model?

So, requirements are very well known,
product definition is stable, technology

is quite understood,
and we are having prior experience

that this technology is suitable for the
implementation.

New version of an existing product.

So, we are creating a new version of the
existing product.

So, as we are having one existing product,
so prior knowledge we are having.

So, porting an existing product to a new
platform.

In this situation, waterfall model can be
adopted, waterfall model can be adopted.

So, in this video, we have discussed what
is waterfall model, what are the

strengths, what are the weaknesses of
waterfall model and when to use waterfall

model in our software development
paradigm.

Thanks for watching this video.

Tutorialspoint.com.

Simply easy learning.

Tutorialspoint.com.

Simply easy learning.