V-Model
Home > Software Quality Definitions - V-Model
SearchSoftwareQuality.com Definitions (Powered by WhatIs.com)
EMAIL THIS
LOOK UP TECH TERMS Powered by: WhatIs.com
Search listings for thousands of IT terms:
Browse tech terms alphabetically:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

V-Model



Word of the Day
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


DEFINITION - 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.

LAST UPDATED: 10 Jul 2007

Read more about V-Model:
- Ram Manohar Tiwari provides a concise overview of the V-Model.
- The Systems Engineering Department at George Mason University illustrates the V-Model concept.
- The Graphical Development Process Assistant (GDPA) at the University of Bremen discusses the technical aspects of the V-Model.


Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Functional testing: Unit testing, integration testing and beyond
Integration tests and unit tests both test the functionality of software, but they alone cannot replace functional testing. Expert Karen N. Johnson...
Successful test-driven development (TDD) with external systems
It's best to think of TDD as a flexible system that does not require unit tests at every compile. It is possible achieve quality results without the...
Unit testing in the enterprise: Five common myths dispelled
Andrew Chessin from Cisco dispels some of the myths that are keeping organizations from reaping the benefits of unit testing.

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...


About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Reprints  |  Site Map




All Rights Reserved, Copyright 2006 - 2008, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts