what is 'v'model?
Answers were Sorted based on User's Feedback
BUssiness Requirements(BR)- ---------> User Acceptence Testing
\ /
System Requirements(SRS)----------> System Testing
\ /
High Level Design(HLD)---------> System ntegratioon Testing
\ /
Low Level Design(LLD)--------> Component Integration Testing
\ /
Coding ------------> Unit Testing
\ /
\ /
\ /
Build
V Model is a popular Software development model. It large
number of resources to implement.
In v model every development stage will have corresponding
testing stage.
Here test will be prepared in parallel with development phases.
i.e
After receiving the business requirements are prepared
then testing team will develop User acceptence Testcases.
But these testcases will be executed and the end of the project.
Here Business Requirements are very abstract in nature and
it talks just about What user/customer actually needs.
System Requirement Specifications will be prepared From
Business Requirements specifications.
SRS will be more elaborated then the Business requirements.
SRS tell what are system features need to be developed.
After seeing SRS Document Testing People will start
preparing System Functional Test cases.
After receiving High level Design Doc,Testing people will
prepare the System Integration Test cases.
After seeing Low level Design doc,Development team will will
prepare the Component integration Test cases.
After coding development team will prepare uint test cases
and executes the unit test on the each individual unit or
function.
Thus there is a mapping between the each development phase
with testing.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / murali
The above answer is partially wright
V model is very simple, checking the application
simultaneously as they developing
Ex
Business scenario's \ / UAT testing
\ /
SRS \ / System testing
\ /
HLD \ / Integration testing
\ /
\ /
LLD \ / Unit testing
\/
Business scenario's - as what the client originally want
Business scenario's is documented that is SRS
HLD and LLD are documented based on the developer
UAT User Accepting testing
Murali,
murali.indrani@gmail.com
9942999500
chennai
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / antu
In V-Model the
strategy goes like this
Gathering phase
User Acceptance Testing.
Analysing
phase System Testing
Design Phase
(HLD and
LLD) Integration Testing
Coding
phase Unit Testing
build
Here unit testing is done related to Coding
Integration testing is based on Design phase
System Testing is done related to Requirements (Analysing phase)
User acceptance is done based on Gathering phase.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / prudwin
V stands for verification and validation
Verification used for document level testing
Validation used for programming level testing
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / xxx
V model is the combination of verification and validation.
verification is done by developer. validation is done by the
tester. In the verification side Design, Coding, Execution
and Implementation whereas in the validation side we had
done Unit testing, system testing, Integration Testing, User
Acceptance Testing.
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / n@n!
There are so many software testing models.
In that model "V" model is one of the model that most of
the companys use.
V model : verification and Validation is nothing but V
model.
Verification/UnConventional/Quality Assurence
Validation/Conventioan/Quality Control
| Is This Answer Correct ? | 0 Yes | 1 No |
Please send me Sample Template on Test Strategy. Tnx in Advance.
can someone give me a brief idea about embedded testing.. i know both embedded system concepts and testing concepts.. i just want to know what we have to do for embedded testing
Random order tests are conducted to exercise different class instance life histories. is it true
Suppose a defect is fixed by developer and that defect got closed. But because of fixing that defect we are getting another defect. If 2nd defect is fixed the 1st defect is reproduced again. If that process is continuing what should the tester do to nail that defect?
Hi friends, Im an MBA Finance, 2 yrs of exp workng in Investment com, + around 2 yrs of exp in Manual testing in Finane domain. Im looking for manual testing jobs but not getting any calls, Im worried is manual tesing in finance domain do have any good scopes in future or not. Plz provide me ur valuable suggestion,so tht I can best decision to retain in this platform(manual testing). or not
What is meant by beta testing?
What is Snapshot Testing? When we need to do and who will involve in this process and also what is the output document of this testing
What is known as data-driven testing?
What r the Macros?
Can any1 tell me what is the use of Shell Scripting on Manual Testing ?
what is meaning of manual testing,,?
iwant know IEEE formate ,how it is used and exactly where it is used? i have details it follows test plan, testcases...etc. i want real time explanation. pls any one give?