diff between water fall model and v-model?
Answers were Sorted based on User's Feedback
Answer / william_vijay
Waterfall model:
in this type of model the flow is sequential starting from
the planning ,design,coding and after that testing is put
into effect .so the testing is after the coding only and
not before that
V-Model:
in this model the testing starts after business
requirements is finished and furnished
and testing continues in paralled with the coding
so that we can eliminate error in the earlier stage
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / sreenu
In the waterfall model we have single phase testing.
That should be after completion of code.
In the v-model we have mutiple phase testing,in every phase
we should use testing.
Is This Answer Correct ? | 4 Yes | 0 No |
water fall model is most expensive model.in this model,
each phase has to be freezed to move to next phase
V model is mapping between development and testing process.
here both team involves simultanious .
main benefit is we can reduce the test design time and also
more flexibilty.
Is This Answer Correct ? | 5 Yes | 1 No |
Answer / andrei
waterfall Model is a very Orthodox method ,systematic and
sequential .This is the most expensive and most time durable
methodology, Every phase is followed sequential.first the
developers build the code and after finishing it the testers
start their job.V Model means displaying everything(build of
code and Testing) under a V symbol.That means the testers
can start their job while the devs work at code..
But the steps are same like waterfall model
1 Requirements analysis
2 Test case design
3 Test case implementation
4 Debugging testing and Validation
5 Deployment and maintenance
Is This Answer Correct ? | 1 Yes | 0 No |
What is test driver and test stub?
can i manage putting fake experience in manual testing what they will do if am caught
What is the maximum length of the test case we can write?
what is meant by acid testing
Who will close the bug and how it is closed..........?
11 Answers HP, IBM,
You need to plan a test project to qualify an application composed of many individual components. Referring to the scenario above, which phases do you expect to take longer than usual?
What is difference between web application and non-web applications?
Do you feel any dis-advantage over the current process? if he/she says any, have You discussed with your Manager reg this ? Why?
Can any one explain the difference between test scenario and test case.
If automating - what is your process for determining what to automate and in what order
What is Internalisation testing?
What is fuzz testing?