Anda di halaman 1dari 16

V Verification and Validation (V&V) is a Systems

Engineering discipline which helps the


development organization to build quality
into the software during the software life
cycle.
V Verification and Validation are the two basic
ingredients of Software Quality Assurance
(SQA) activities
—wo approaches to building software:
O Build software, fix things afterwards

O Building quality into software


V !eneric definition of V&V by the IEEE [Standard
of !lossary of Software Engineering —erminology]
O aequirements for a system or component are
complete and correct
O Products of each development phase fulfill the
requirements or conditions imposed by the
previous phase
O Final system or components comply with
specified requirements
= IEEE Standard defines „  
 as
the Dzprocess of evaluating a system or
component to determine whether the products
of a given development phase satisfy conditions
imposed at the start of the phasedz.
= —hat is to say, software verification is
concerned with the degree of acceptability of
a product for a particular phase.
= Verification is the process of determining whether
or not the products of a given phase of software
development meet all the constraints established in
the previous phase (Standard !lossary of SE
—erminology)

= Verification is review of interim work steps and


interim deliverables during a project to ensure they
are acceptable.

= Also known as Static —esting


V aequirement reviews
V Design reviews
V Code walkthroughs
V aequirement tracing
= Validation is the process of evaluating software at the
end of the development process to ensure compliance
with the initial requirements

= Validation testing is conducted to ensure that the


software meets the functional, behavioral &
performance requirements of the system

= Also known as Dynamic —esting


V hite box testing
V Black box testing
V !rey box testing
V Different —ypes of —esting
V Verification and validation should establish
confidence that the software is fit for
purpose.
V —his does NO— mean completely free of
defects.
V aather, it must be good enough for its
intended use and the type of use will
determine the degree of confidence that is
needed.
= Validation is concerned with checking that the
software meets the user's needs and/or
objectives, and

= Verification is concerned with checking that the


system is well engineered.

Software testing is one element of a generic


process referred to as Verification & Validation
in engineering software systems
V Quality Assurance (QA) refers to the process
used to create the deliverables, and can be
performed by a manager, client, or even a
third-party reviewer. Examples of quality
assurance include process checklists, project
audits and methodology and standards
development.
V Quality Control (QC) refers to quality related
activities associated with the creation of
project deliverables
V Quality Assurance is process oriented and
focuses on defect prevention; while quality
control is product oriented and focuses on
defect identification.

V Quality Control (QC) refers to quality related


activities associated with the creation of
project deliverables
V Quality control is about adherence to
requirements. Quality assurance is generic
and does not concern the specific
requirements of the product being
developed.
V Quality assurance activities are determined
before production work begins and these
activities are performed while the product is
being developed. In contrast, Quality control
activities are performed after the product is
developed.