what is verification, validation
Answers were Sorted based on User's Feedback
Answer / sudhakar8
Verification is process of confirming whether software
meets its specifications.
Validation is process of confirming whether software meets
user requirements
Is This Answer Correct ? | 10 Yes | 0 No |
Answer / sudir
For the above question i'm explaning definitions with
logical reason.
Verification:
Verification typically involves reviews and meetings to
evaluate documents, plans, code, requirements, and
specifications.
The determination of consistency, correctness &
completeness of a program at each stage
Validation:
Validation typically involves actual testing and takes
place after verifications are completed.
The determination of correctness of a final program with
respect to its requirements.
I hope you got it....
Thx,
Sudir
sudir.csc@gmail.com
Is This Answer Correct ? | 5 Yes | 0 No |
Answer / lakshmi
Verification - Are we building the Product RIGHT
This is to ensure that the Software product is build the
right way
Validation - Are we building the RIGHT product
It is the testing done to ensure that the product works as
expected,
Is This Answer Correct ? | 3 Yes | 0 No |
Answer / jayanthi
Verification is process of confirming whether software
meets its specifications.
Validation is process of confirming whether software meets
user requirements
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / rudraneel
VERIFICATION :
Verification specifies as per requirements the application
or the product is developed or not.
->It is a Static Testing
->Involves Inspection,Walk-through,Peer-review
VALIDATION :
Validation specifies as per user need the application or
the product is working or not.
->It is a Dynamic Testing
->Involves BBT & WBT
Is This Answer Correct ? | 1 Yes | 1 No |
Answer / nandankumar
Verification:
"Verification is a process of checking each and every role in a organization in order to confirm, whether they are doing their work according to the companies process guidelines or not"
Verification starts from 1st phase of SDLC and continues up to the last phase of SDLC. and normally this falls under unconventional testing.
Normally verification is done by Quality Assurance people and falls under Unconventional Testing.
And starts from 1st phase of sdlc and continues up to last phase of sdlc.
Even testing phase also verification will be there.
Validation :
" Validation is a process of checking conducted
on the developed product or it related parts in order to confirm whether they are working according to the expectations or not".
Validation starts from coding phase of sdlc and continues up to last phase of sdlc.
It is done by the Quality Control People.
And Validation falls under Conventional Testing.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / vijay
verification invovles on the one side of the v-model i.e
crs,srs,hld ,lld and validation means system and functional
testing.
othermeaning is tat right product to build is verification
product right build is validation
Is This Answer Correct ? | 0 Yes | 1 No |
verification is the first steps
validation is the next steps , ie checking the verification
is done correctly or not are examined by tester
Example : object questions are corrected by students is
verification , next steps checking same answers by the
staff is called by validations
Is This Answer Correct ? | 0 Yes | 2 No |
Answer / rohini
v-stands for verification and validation.
VERFICATION:it specifies testing on documents like
CRS,SRS,HLD and LLD'S.
VALIDATION:it specifies testing on programs,programs
interconnection,software and changes in s/w.
Is This Answer Correct ? | 0 Yes | 3 No |
How do u prepare test environment for ur application?
1.Difference between Project & Product? 2.What is Tst Case,Test index & Test Senarios? 3.Difference between QA & QC
What is bug release?
is tha integration testing include non functional test?
What is Change Management?
0 Answers Cap Gemini, MicroGenesis,
what is the difference between sanity testing and smoke testing.
Tell me a critical defect in which your Client,PM,PL appreciate on you
How can it be known when to stop testing?
what can't be automated on the projects?
give on example of regression testing, u did in yuor projec?
Efficient % is calculated at which level?
I saw the term 'Idiot Proofing' under White box test techniques. Really what does it mean?