Editing V-model (section)

== Types ==
There are three general types of V-model.

=== V-Modell ===
"V-Modell" is the official project management method of the German government. It is roughly equivalent to [[PRINCE2]], but more directly relevant to software development.<ref>[https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/V-Modell-XT/vmodell_xt_node.html "V-Modell site (in German)"], accessed July 10, 2020.{{Dead link|date=November 2024}}</ref>  The key attribute of using a "V" representation was to require proof that the products from the left-side of the V were acceptable by the appropriate test and integration organization implementing the right-side of the V.<ref>German Directive 250, Software Development Standard for the German Federal Armed Forces, V-Model, Software Lifecycle Process Model, August 1992</ref><ref>{{cite web |title=Fundamentals of the V-Modell |url=http://v-modell.iabg.de/v-modell-xt-html-english/349ffba5c5cda0.html#toc12 |access-date=17 Nov 2024}}</ref><ref>{{cite web |title=V-Modell XT, Part 1: Fundamentals of the V-Modell |url=http://ftp.uni-kl.de/pub/v-modell-xt/Release-1.1-eng/Dokumentation/pdf/V-Modell-XT-eng-Teil1.pdf |access-date=17 Nov 2024}}</ref>

=== General testing ===
Throughout the testing community worldwide, the V-model is widely seen as a vaguer illustrative depiction of the software development process as described in the [[International Software Testing Qualifications Board]] Foundation Syllabus for software testers.<ref>[http://www.istqb.org/downloads/viewdownload/16/15.html "International Software Testing Qualifications Board – Foundation Level Syllabus"], accessed January 9, 2013.</ref> There is no single definition of this model, which is more directly covered in the alternative article on the [[V-Model (software development)]].

=== US government standard ===
The US also has a government standard V-model. Its scope is a narrower systems development lifecycle model, but far more detailed and more rigorous than most UK practitioners and testers would understand by the V-model.<ref>{{cite web | url=https://ops.fhwa.dot.gov/publications/seitsguide/seguide.pdf | title=Systems Engineering for Intelligent Transportation Systems| publisher=US Dept. of Transportation|page=10| access-date=June 9, 2007}}</ref><ref>[https://www.fhwa.dot.gov/cadiv/segb/index.cfm "US Dept of Transportation, Federal Highway Administration. Systems Engineering Guidebook for ITS"], accessed January 9, 2013.</ref><ref name=VPM>Forsberg, K., Mooz, H., Cotterman, H. ''Visualizing Project Management,'' 3rd edition, John Wiley and Sons, New York, NY, 2005. Pages 108-116, 242-248, 341-360.</ref><ref name=INCOSE>International Council On Systems Engineering (INCOSE), ''Systems Engineering Handbook Version 3.1,'' August 2007, pages 3.3 to 3.8</ref><ref>{{cite web
| url = http://www.dau.mil/pubscats/PubsCats/AR%20Journal/arj53/Redshaw53.pdf
| title = BUILDING ON A LEGACY: RENEWED FOCUS ON SYSTEMS ENGINEERING IN DEFENSE ACQUISITION
| access-date = 14 Apr 2016}}</ref><ref>{{cite web
| url = https://insights.sei.cmu.edu/sei_blog/2013/11/using-v-models-for-testing.html
| title = Using V Models for Testing 
| date = 10 November 2013 
| access-date = 14 Apr 2016}}</ref>