   V-Model
  Hi guys!Anyone of you familar with the V-Model in software engineering?(http://en.wikipedia.org/wiki/V-Model)Just one simple question: Why is it V shaped?What exactly is the connection between steps on the same level?Thanks!   
  The results of the left arm of the V are verified by the processes in the right arm.Examples:* The detailed design is verified by QA testing* The high level concept is verified after roll outThis means, steps that are taken early in development can only be verified very late, making it very important to get them right.Note that this problem is not a problem of the V-Model, but is a general problem. The V-Model merely tries to make everyone aware of those issues.Actually, the first sentence of the Wikipedia states the purpose of the V-Model quite clearly:"The V-Model (or VEE model) is a systems development model designed to simplify the understanding of the complexity associated with developing systems.[2][3][4] In systems engineering it is used to define a uniform procedure for product or project development."Software engineering in general is more flexible than the V-Model may make you believe. Often substantial changes (i.e. changing the Hardware or OS) can be made without throwing everything else away. In other industries, mistakes made in the concept phase will invalidate everything done afterwards.;  Great, thanks for the detailed explaination.  :-D   