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

Software validation and verification.

So, it sounds that this validation and
verification are very similar,

but they are totally different.

So, let me discuss on them into more
details.

So, at first we are going to discuss
software validation.

So, validation is a process
of examining whether

or not the software satisfied
the user recommends.

It is carried out at
the end of the SDLC,

that is the software
development life cycle.

If the software matches the recommends for
which it was made and it is validated.

That means, really the
software whatever we are

developing is in accordance
to the user's recommend.

So, there is a main theme in case of
software validation.

So, validation ensures
the product under

development is as per the
user's recommend or not.

So, you know that at the very early stage
of this SDLC, we usually gather all the

recommend from the users,
from the stakeholders in the

problem domain and from
there we make a recommend list.

So, after getting that recommend list,
we are having certain other phases and

then we go for the software development
and the respective implementation.

So, in case of software validation,
we usually check that this validation

ensures the product under development is
as per to this user recommend or not.

So, validation answers the question,
are you developing the product which is,

which attempts all that user needs from
the software.

So, that question is to be answered in
case of validation.

So, validation emphasizes on user
recommends.

So, now let us discuss the software
verification.

So, software verification.

So, verification is the process of
conforming, if the software is in

accordance with the business
requirements or not and is

developed adhering the proper
specifications and methodologies.

So, whether this particular software is in
accordance with the respective business

requirements or not and whether you are
using the proper specifications So,

verification ensures the
product being developed

is according to the
design specifications.

So, whatever we have planned, whatever the
design specifications, methodologies,

we decided whether that
same methodology, same design

specifications have been
maintained throughout.

So, that will be verified in this
verification phase.

So, verification answers the question,
are we developing this product Start by

firmly following all the design
specifications.

So, there is a question, which will be
asked here.

And verification concentrates on the
design and the system specifications.

So, actually you see,
in case of software

validation, we are concerning
with the requirements.

In case of software verification, we are
concerning with the required specifications.

Now, in the next slide, we are going to
discuss different terminologies.

So, at first, we are going to discuss
errors.

So, what is the error?

So, this is the actual coding mistakes
made by the developers.

In addition, there is a
difference in output of software

and the desired output and
it is considered as an error.

So, the source of the error is the
mistakes done by the developer.

Now, what is the fault?

When error exists, fault occurs.

So, if fault also known
as a bug as a is a result

of an error which can
cause system to fail.

So, error is the cause and fault is the
effect.

Next one is the failure.

Failure is said to be the
inability of the system to

perform the desired task
and that is known as a failure.

Failure occurs when the fault exists in
the system.

So, due to errors the
faults will occur and due

to faults this failure
will occur in the system.

So, failure means the
respective software is failed to

perform some activity and
the desired task in the system.

So, that is known as a failure.

Now, here we are having quality control
activities.

So, I have listed everything into one
slide.

So, we will be having
several videos on most of

this particular topics
separately dedicatedly.

So, let me just review this diagram for
you.

So, quality control deals with this fault
avoidance.

And fault avoidance can be done in this
three or four different ways.

There is a development
methodology, configuration

management,
verification and the review.

With the help of this, this fault
avoidance can be achieved.

Next one is the fault detection.

So, first one is the first technique is
the debugging.

Debugging can be of two types.

One is the correctness
of the answers getting

generated and the
respective performances.

Now, this fault detection can also be done
using testing.

So, there is a system testing,
component testing, integration testing.

So, there are other testing methods are
available.

When having this fault tolerance,
when having the atomic transactions we

require and the modular redundancy should
be checked.

So, in this way, the quality control
activities which is applicable in a

software development process has been
listed in the same in a single page here.

So, in this case, we
have discussed what is the

software validation
and software verification.

What are the differences between them?

And what is error?

What is fault?

And what is failure?

Thanks for watching this video.

TutorialsPoint.com.

Simply easy learning.