The Ultimate Guide to the SDLC

The Complete and Ready-To-Adapt System Development Life Cycle

  • Home
  • SDLC Principles
  • Articles
  • Table of Contents
  • Downloads
You are here: Home / SDLC / A Funny Thing Happened on the Way to the V-Model

A Funny Thing Happened on the Way to the V-Model

By Victor M Font Jr Leave a Comment

Forsberg & Mooz (2006) - Used with Permission
Forsberg & Mooz (2006) – Used with Permission
In the late 1980s two countries, Germany and the United States, simultaneously but independently developed a V-Model. While the two models are similar in concept, they differ enough to be considered alternative approaches. The German V-Modell was developed in part by IABG in Ottobrunn, near Munich in cooperation with the Federal Office for Defence Technology and Procurement in Koblenz for the Federal Ministry of Defence. IABG was founded in 1961 as a central analysis and testing organization for Germany’s aeronautics industry and the Ministry of Defence. Their focus was aeronautics industry testing and security and defense analysis. Today, IABG is a leading European technology and science service provider and is involved with the Airbus development programs.

Development of the V-Modell occurred over a 4-year period beginning in 1986. Pilot project trials started in early 1990. It was made obligatory for the defense area by the Federal Ministry of Defence in February 1991. The V-Modell proved so successful in Germany’s defense industry that in the summer of 1992 it was taken over by the Federal Ministry of the Interior for the civilian public authorities domain to provide a uniform systems development standard for the whole range of public authorities. With the publication of the “Development Standards for IT Systems of the Federal Republic of Germany” in 1997, the V-Modell 97 entered into force as the standard for all civil and military federal agencies. It was used throughout Germany by banks, insurance companies, car manufacturers, the manufacturing industry and energy producers.

The V-Modell gained traction in Europe. An English translation was completed for use in international projects. It is the subject of a European Commission (EC) project started in 1989 with the goal of surveying software engineering methods and harmonizing them. The German representative to the EC Committee is the Federal Ministry of the Interior. In view of the Ministry’s own use of the V-Modell, it was nominated as the German standardization contribution at the European level.

The German V-Modell was structured into four functional parts called submodels. The submodels are:

  • Software Development (SWD)
  • Quality Assurance (QA)
  • Configuration Management (CM)
  • Project Management (PM)

These four are closely interrelated and mutually influence one another through the exchange of products/results. Since the focus of our SDLC is systems development, let’s decompose the software development submodel. The submodel comprises the following nine primary activities:

  1. System Requirements Analysis and Design:
    1. Describes the system requirements its environment
    2. Conduct a threat and risk analysis; develop a security concept
    3. Deliver a user level model of functions/data/ objects
    4. Structure the system into subsystems, segments or configuration items
  2. DP Requirements Analysis and Design
    1. Describe the DP segment requirements and its environment
    2. Development of a security model, structuring the segment into its SW and HW configuration items
  3. SW Requirements Analysis
    1. Describe the SWCI requirements and its environment
  4. Preliminary Design
    1. Structure the SWCI in SW components/modules/database, specification of the interfaces and interaction of its elements
  5. Detailed Design
    1. Describe the components and modules with respect to the real implementation of their functions, the data administration and error handling up to a programmig specification
  6. Implementation
    1. Convert the programming specifications to statements of the programming language
    2. Perform informal assessment of developed code and implementation of a database (if required)
  7. SW Integration
    1. Integrate modules to components and components to the SWCI
  8. DV Integration
    1. Integrate the different SW and HW configuration items to a DP segment
  9. System Integration
    1. Integrate the subsystems (if existing) and segments to the system

V-Modell 97 met with obsolescence in 2004. It no longer reflected the state-of-the-art of information technology and its use declined. New methods and technologies—as for example component-based development or the test-first approach—are considered only to a limited degree in V-Modell 97. It is superseded by “V-Modell XT,” completed in 2006. The V-Modell XT is a standard developed on behalf of the Federal Office of the Bundeswehr for Information Management and Information Technology and the Federal Ministry of the Interior, Central Office for Information Technology Coordination in the Federal Administration (BMI-KBSt).

UltimateSDLC.com runs on the Genesis Framework

The Genesis Framework empowers you to quickly and easily build incredible websites with WordPress. Genesis provides the secure and search-engine-optimized foundation that takes WordPress to places you never thought it could go.

Check out the incredible features and the selection of designs. It's that simple—start using Genesis now!

Click here to download The Genesis Guide for Absolute Beginners (PDF - 1.4 MB)

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Buy Now, Instant Download

The Ultimate Guide to the SDLC front cover
PDF eBook

$49.99

Add to Cart

Download Free Preview

$0.00Free Download

UltimateSDLC.Com is Hosted on SiteGround

SiteGround Web Hosting

Testimonials

Thank You for Your Testimonial

“…The author has truly “hit the nail on the head.” Whether you are an academic student who is aspiring to be an IT professional one day, a trainee that has just started career, a business & quality analyst and manager that has years of IT SDLC project experience—a must read for an IT professional at all levels of IT journey.” —Sekhar Bommana PMP, ITIL, VP – … Read More

Consulting Services

I have the prescription for your IT ailments

Implementing a SDLC is not an easy task. In fact, it can take months or even years to develop the policies, processes, procedures, metrics and training to bring you the kind of results that lead to repeatable project successes, reduced rework and deliverables that meet or exceed stakeholder expectations. There are a number of factors that … Read More

Connect with the Author

  • Email
  • Facebook
  • LinkedIn
  • Pinterest
  • Twitter
  • YouTube

Copyright Notice

Copyright © 2010–2023 Victor M. Font Jr.
Unauthorized use and/or duplication of this material without express and written permission from this website’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Victor M. Font Jr. with appropriate and specific direction to the original content.

Recent Posts

  • Managing Scope Creep
  • Agile Manifesto
  • Adaptive Software Development
  • Incremental Commitment Model
  • Legend of the Chicken and Pig

Recent Comments

  • Gold on The Project Management Method and the SDLC
  • Phineas on Adaptive Software Development
  • Victor M Font Jr on US Vee Model
  • Jessica Tattersall on US Vee Model
  • Aditi on IT Governance and the SDLC – Part 1

Tags

Affiliates Agile Best Practice Business Analysis Checklist Commission Elicitation Good Requirements Hybrid Hyrid IT Governance Model Organizational Change Outsourcing Project Management Quality Assurance Requirements Elicitation Risk Management SDLC Thought Provoking Waterfall Waterfall Variant

Return to top of page

Copyright © 2010–2023 Victor M. Font Jr.

Privacy Policy | Terms of Service | Contact Author | Report Erratum | Sitemap