Explain the V-Model?

Answer Posted / pavan

The V model gets its name from the fact that the graphical representation of the different test process activities involved in this methodology resembles the letter 'V'. The basic steps involved in this methodology are more or less the same as those in the waterfall model. However, this model follows both a 'top-down' as well as a 'bottom-up' approach (you can visualize them forming the letter 'V'). The benefit of this methodology is that in this case, both the development and testing activities go hand-in-hand. For example, as the development team goes about its requirement analysis activities, the testing team simultaneously begins with its acceptance testing activities. By following this approach, time delays are minimized and optimum utilization of resources is assured.

Is This Answer Correct ?    6 Yes 3 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

Explain the requirements?

599


What is meant by Regression testing? Differentiate Sanity and Regression testing?

1844


What is bottom-up strategy?

603


What is control structure testing?

614


What is different type testing you done when doing webbase application.the desktop application

1501






What is system test?

563


What is test result analyzer?

742


What is glossary of software qa/testing?

594


What is testing type and what are the commonly used testing type?

587


What goes into a Test Summary? How would you write a Test Summary?

1731


HI to all this is dinakar i am planning to write istqb foundation level exam but i dont have the material so any one have material regards that one please send to my id was dinakarmails@gmail.com thanks alot in advance

1506


What is a test closure?

582


What are different types of protocols used in transportation and session layers of SAN?

1429


Testing activity which is performed to expose defects in the interfaces and in the interaction between integrated components is?

662


What is the main objective when reviewing a software deliverable?

812