Académique Documents
Professionnel Documents
Culture Documents
Developed by
Abhijeet Savkar
Contents
Verification and Validation
Severity and priority
Bug life cycle
Verification
The process of evaluating
Validation
The process of evaluating software during or at the
end of development process to determine whether
it satisfies specified business requirements.
To ensure that the product actually meets the Users
needs, and that the specifications were in the first
place . In other words, to demonstrate that the
product fulfills its intended use when placed in its
intended environment.
Software should do what the user really requires
Testing
Verification
Validation
Static technique
Non execution of
code.
Human base
checking of
document or files.
Dynamic technique
Execution of code
Computer base
execution of program
Verification
Validation
Verification uses
methods like
inspections, reviews,
walkthroughs, and
Desk- checking
Validation
uses
methods like black
box
(functional)
testing,
gray
box
testing, and white box
(structural)
testing
etc.
Verification
Validation
Verificationis to
that validation
cannot catch. It is
low level exercise.
Validationis to
check whether
software meets the
customer expectations
and requirements.
It can catch errors
that verification
cannot catch. It is High
Level Exercise.
Verification
Validation
Target is
requirements
specification,
application and
software
Target is actual
architecture, high
level, complete
product-a unit, a
design, and database
module, a bent of
design etc.
integrated modules,
and effective final
product.
Verification
Validation
Verification is done
by QA team to
ensure that the
software is as per the
specifications in the
SRS document.
Validation is carried
Severity
Priority
Priority defines the order in which we should
resolve a defect.
Should
References
Google.com
Thanks
you