 - The V-Model, also called the Vee-Model, is a product-development process originally developed in Germany for government defense projects. It has become a common standard in software development. The V-Model gets its name from the fact that the process is often mapped out as a flowchart that takes the form of the letter V.
The development process proceeds from the upper left point of the V toward the right, ending at the upper right point. In the left-hand, downward-sloping branch of the V, development personnel define business requirements, application design parameters and design processes. At the base point of the V, the code is written. In the right-hand, upward-sloping branch of the V, testing and debugging is done. The unit testing is carried out first, followed by bottom-up integration testing. The extreme upper right point of the V represents product release and ongoing support.
The V-Model has gained acceptance because of its simplicity and straightforwardness. However, some developers believe it is too rigid for the evolving nature of IT (information technology) business environments.
 |
Learn more about Software unit testing |
| Better software through debugging and unit testing: Bugs plague software project big and small, and today's complicated software makes debugging more difficult than ever. Let these tips, tutorials, podcasts and articles help you. |
| Unit testing critical for improving software quality: With unit testing, programmers can catch bugs early before they cause problems. It's important to encourage such testing and not scare programmers with extreme testing practices. |
| Beautiful Code -- Chapter 7, Beautiful Tests: This excerpt written by Alberto Savoia shows how a broad, creative approach to testing can not only eliminate bugs but help programmers do their jobs better. |
The Way of Testivus … or How to Complete Projects Ahead of Schedule: or How to Complete Projects Ahead of Schedule
Here's a unique booklet that drives home the importance of software testing, particularly unit testing. |
| Better software through debugging and unit testing: Bugs plague software project big and small, and today's complicated software makes debugging more difficult than ever. Let these tips, tutorials, podcasts and articles help you. |
| Better software through debugging and unit testing -- Other useful resources: Here is a list of books, blogs and Web sites that can offer you more information on debugging, unit testing, XP and test-driven development. |
| Better software through debugging and unit testing -- Unit testing, Extreme Programming and TDD: Unit testing is a key element of Extreme Programming (XP) and test-driven development (TDD). These tips, tutorials and articles will help you further understanding unit testing. |
| Better software through debugging and unit testing -- Unit testing basics: Unit testing is critical part of the debugging process. These tips, tutorials and podcasts explain what unit testing is and how to effectively conduct them. |
The Way of Testivus … or How to Complete Projects Ahead of Schedule: or How to Complete Projects Ahead of Schedule
Here's a unique booklet that drives home the importance of software testing, particularly unit testing. |
| LAST UPDATED: |
10 Jul 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
 |
 |
| |
RELATED GLOSSARY TERMS
| Terms from Whatis.com − the technology online dictionary |
 |
mock object
(SearchSoftwareQuality.com)
A mock object is a simulated object that mimics the behavior of a real object in controlled ways. Mock objects are often employed in unit testing to...
|
|
unit testing
(SearchSoftwareQuality.com)
Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and...
|
|
|
Show me everything on 
