Talk:V-Model

From Wikipedia, the free encyclopedia

WikiProject Systems (Rated Start-Class)
	This article is within the scope of WikiProject Systems, which collaborates on articles about the idea of systems. If you would like to help, you can edit this article or visit the project page, where you can join the project and/or contribute to the discussion.
Start	This article has been rated as Start-Class on the assessment scale.
Mid	This article is on a subject of mid importance within Systems.
Help with this template This article has been rated but has no comments. If appropriate, please review the article and leave comments here to identify the strengths and weaknesses of the article and what work it will need.

Contents 1 Proposed for deletion 2 Confused 3 Mergeto V model 4 VDI Standard for developing mechatronic systems 5 How is it pronounced? 6 Removed from the article

[edit] Proposed for deletion

This article was proposed for deletion Feb. 2005. Wikipedia:Votes for deletion/V-Modell. Joyous 19:56, Feb 26, 2005 (UTC)

There is a reference near the bottom of the page to an explanation of the v-model in french. That french page is quite interesting and describes the v-model known more widely. (I wish I could remember the reference.) The english page is not about the same subject at all and should not be linked to from the english language v-model page. V-model is not the same as v-modell.

[edit] Confused

Although I found a source (and cited it too on the article page) that said both V-model and VEE model is the same, I am still confused. I was looking for the VEE model as often talked about in Systems engineering. The one here, and further discussed as a Software development process is probably same. However, now, I am not sure about V-modell with a double l. Please discuss it here, or link to sources if you know what's going on. Perhaps the purpose of this page can be to disambiguate between V-model, VEE-model, and V-modell Gnusbiz 20:28, 9 June 2007 (UTC)

V-Modell is a software engineering process model developed by the German Bundeswehr (armed forces) in 1991, revised in cooperation with the German Department of the interior in 1992, 1997 and 2005. I have added a link to the complete English documentation right to the end of this dicussion page. It is the standard for all projects that deal with German authorities.--DasWoelfchen 21:43, 23 October 2007 (UTC)

[edit] Mergeto V model

The V model in software development is essentially the same V model that was devised in 1980s as a project management/product development tool. The German wikipedia page is more elaborate on this see [1]. It appears that the V model or VEE model (as it is called in systems engineering) is often customized for an industry. Then of course, there is a confusion regarding "V modell". I suggest we merge the V-Model (software development) page into the main page as a section and highlight the differences there. Gnusbiz 17:07, 11 June 2007 (UTC)

I Wikified the article and made it more apply to Systems Engineering. Maybe now this is more clear we can forget about the merge (although you are right that it is still the same model) - Mdd 15:14, 18 September 2007 (UTC)

Well, what might contribute to the confusion is the fact that the V-Modell deals with both, pure software development as well as (embedded) hardware development - due to its military origin (cf. the references to the VDI sources below). Anyway, both variances share the same characteristics and main tasks, so a merge could be a good idea. If you need somebody that sheds some light upon the German V-Modell article, please let me know!--DasWoelfchen 22:03, 23 October 2007 (UTC)

[edit] VDI Standard for developing mechatronic systems

Hello, the V-Modell is core part of VDI2206 "Design methodology for mechatronic systems" of the German Association of Engineers (VDI), see: [2] (Hint: Don't read it, the English translation is terrible...)

The VDI 2206 guideline (for mechatronic systems development) is the successor of the VDI 2221 (mechanical development; for example: Pahl/Beitz, 1988) and the VDI 2422 (Electrical development). Actually, the VDI 2206 adopts the Spiral Model form Software development (Boehm, 1987), but mix SW+ME+EE alltogether and compatible with each other.

The V-model approach is quite useful because you can use it for all kind of technical development projects: from technology development, over platform development, application development, variant design, down to production ramp-up, production relaunch.

Some Sources:

• http://www.cam.uni-sb.de/publikationen/paper/cirp_budapest_2004.pdf
• http://csdl.computer.org/comp/proceedings/compsac/2004/2209/01/220910584.pdf
• http://www.md.kth.se/~fredrikr/AM2D/OSTT.pdf
• http://www.nt.ntnu.no/users/skoge/prost/proceedings/ifac2005/Fullpapers/05172.pdf

Suggestion: Put the V-Model (software development) into this section, and show:

1. Inputs of a "macro cycle": Requirements (depends on the kind of project, e.g. customer requirements, previous technical development project, previous "macro cycle", etc.)
2. common tasks of the "macro cycle", e.g.
3. systems design (of SW+ME+EE; usually done by cross-functional skilled systems engineers or a team of discipline architects) and
4. systems integration (of SW+ME+EE; usually done by quality assurance people)
5. different tasks of the "macro cycle", i.e. when SW and ME and EE are working seperatly (usually specialists within an discipline or within engineering departments, e.g. software programmer, mechanical design/engg, electrical/electronic design/engg)
6. Outputs of a "macro cycle", e.g. analytical protottypes, functional models, A-, B-, C-,... prototypes (from here manufacturing engineers and supplier engineers step into the scene...), pilot production models, mass-produced prodcuts,...
7. Mechatronic? (<- Isn't that a Transformer?) Denglish bitter?

Without additional review I'm not for merger. Luis F. Gonzalez 17:57, 18 June 2007 (UTC)

[edit] How is it pronounced?

Do the German's really call it the "Vee Model", as in "Wie" model or is it "Fau" model?
Just watchen the Blinkenlichten... Luis F. Gonzalez 17:57, 18 June 2007 (UTC)

Yes, you're right it is rather pronounced "Fau Modell" (speaking F as in fish, AU as the OU in house and put the emphasis on the second syllable of Modell, as you would do in the word Hotel). As lots of the German Geeks and IT specialists use to speak a German dialect - let's call it Denglish - some of them tend to call it "Vee Model". By the way, the Blinklichten stuff is really funny - from a German perspective - although the plural of Blinklicht in German is Blinklichter (just to fulfill the prejudice of the German humourless correctness ;)) --DasWoelfchen 21:14, 23 October 2007 (UTC)

[edit] Removed from the article

I removed the following text from the article because it doesn't seems to be related to the V-model in systems engineering - Mdd 14:32, 18 September 2007 (UTC)

The current version of the V-Model is the V-Model XT (http://www.v-modell-xt.de) which was finalized February 2005. It is not really comparable to CMMI. While CMMI only describes "What" has to be done, the V-Model also describes "How" and "When" it has to be done and "Who" is responsible for doing it.

If you want to know more about the V-Modell XT please refer to this English document V-Model XT Complete Documentation. I have added this link as well to the link-list in the document. If you think that is inappropriate, please feel free to remove it!--DasWoelfchen 21:30, 23 October 2007 (UTC)