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

We are going to discuss another software
development paradigm that is our V model.

So, the major drawbacks of
waterfall model is we move to

the next stage only when
the previous one is finished.

And there was no chance to go back if
something is found wrong in the later stages.

So, in because of waterfall model,
we cannot replace our path.

Whenever one phase is getting completed,
we are moving to the next stage.

And if you find that there was some errors
in the earlier stages or phases,

we cannot do anything there.

So, V model provides means of testing of
software at each stage in reverse manner.

So, that is the main theme behind this V
model.

So, V model provides
means of testing of

software at each stage
in the reverse manner.

So, we shall discuss this one using this
diagram.

So, the first phase will be having our
requirement gathering.

Next phase will be the system analysis.

Next phase will be the software design.

Next, we are going to design the modules
and then we are going for the coding.

So, going through all these phases,
then the coding will be initiated.

Now, the next phase will be unit testing.

Now, what is unit testing?

Well, we shall test each and every module
individually.

So, this module design is corresponding to
this unit testing.

So, they are correlated in that case.

So, in case of unit testing, we shall
check whether each and every module which

is requiring, might be requiring some
input parameters.

We shall give those input parameters.

And whether we are getting the required
output as a return, the required output as

a return with the, with the correct
calculated values and specifications

defined, are they working well
individually?

So, that will be done in this unit
testing.

So, unit testing is commensurating with
this module design.

Next one, we are having this integration
testing.

And this integration testing is
commensurating with this software design.

In case of integration testing,
we shall test how these modules are

getting interrupted, how these modules are
cooperating with each other.

So, wherever a module is passing the right
parameter in the right format to another

module, if it is so, are they working
well?

Are they communicating well?

So, that testing will be done in case of
integration testing.

Next testing will be the
system testing, which

is commensurating
with this system analysis.

So, you should check whether this whole
system comprising of multiple different

modules and interaction between the
modules, whether the whole system is

working fine, according to the requirement,
according to the desired level or not.

So, that will be done in the system
testing.

And next one will be the acceptance
testing.

And according to the requirements,
whatever we gathered at the very first

stage, Is the software is producing
the same and implementing

the all requirements whatever
was mentioned at the early stage.

So, that is known as the acceptance
testing that will be done by the,

by the user also can be done by the user
also.

And they will check whatever the
requirements they gave whether this

particular software is in accordance with
that or not.

So, that will be done, that testing will
be done in the acceptance testing.

So, at every stage, test plans and test
cases are created to verify and validate

the product according to the requirement
of that stage.

So, in the previous diagram, we have also
mentioned that here we are having the

verification phases and here we are having
the validation phases.

For example, in requirement gathering
stage, the test team prepares all the test

cases in correspondence to the
requirements.

Later, when the product is developed and
is ready for testing, test cases of this

stage verify the software
against its validity

towards the
requirements at this stage.

So, whenever we gather the requirements,
there we plan some test cases.

When the software is getting is going to
get delivered.

And when the acceptance testing is getting
done, in that case, we can we can run this

test cases and we can check whether this
software is going to give us the correct

answer in the correct format with the
correct precision.

This makes both the verification and
validation go in parallel.

This model is also known as verification
and validation model.

So, other than V model, this particular
model can also be called as verification.

So, now, we are going for the strengths of
this V model.

So, which phase is more emphasized when
using V shaped model?

So, this is a question.

In that case, answer should be like this.

Emphasize planning for verification and
validation of the product in early stages

of the product development.

And each derivative must be testable.

More emphasis laid on the testing phase.

Ease of use?

Answer is easy to use.

So, this model is easy to use and
implement.

Can V model handle concurrent events?

So, now, we are considering the weaknesses
of V model.

So, the first question
whatever you are considering

here, can V model
handle concurrent events?

The answer is does not easily handle
concurrent events.

Next one is can V model handle dynamic
changes in requirements?

The answer is does not easily handle
dynamic Great changes in the requirement.

All these requirements should be known
beforehand.

Does V-model contain risk analysis
activities?

So, does not contain any risk analysis
activities, which you observe in our

spiral model, which we discussed in the
respective video on spiral model.

So, now next question is that when to use
the V-model?

So, these are the cases where you can use
this V-model.

These are the solutions we can give.

So, excellent choice for systems requiring
high reliability and hospital patient

control applications in those cases is
V-model can be implemented.

All requirements are known upfront,
because V-model is not suitable for those

cases where the requirements will be
coming during the software development

phases, when it can
be modified to handle

changing requirements
beyond analysis phase.

And solution and technology are known to
us.

We are having private
experience working on them,

because there is no
risk analysis phase here.

So, the technology in
which you are going to

develop the software
must be pre-known to us.

Thanks for watching this video.

TutorialsPoint.com Simply easy learning.