Previous Next V-Model Official Homepage by IABG  
Lifecycle Process Model: Preliminaries  

  Vorgehensmodell: Vorbemerkungen

  • Preliminaries
  • 1 Objective and Application of the Lifecycle Process Model
  • 2 Introduction to the V-Model
  • 3 General Regulations


    The Development Standard for IT Systems of the Federal Republic of Germany (EStdIT) regulates all activities and results of IT Systems development and of IT systems maintenance/modification. This standardization is realized on three levels:

    This standard is meant as a technical rule and a supplement to GD 220. It addresses the departments in charge of the realization; its objective is to minimize the great variety of methods and tools applied.

    This standard is to be applied for the development of IT systems for the Federal German Armed Forces. This also includes IT portions in systems, no matter if software is developed internally or within the scope of orders placed externally by industry.

    If marketable components are used as a core for the solution or as solution for the whole system then these off-the-shelf-products have to be treated in accordance with the regulations of the V-Model (see section 3: General Regulations and Part 3 Collection of Manuals).

    In case the software products are not subject to software maintenance and modification (SWMM) by the Federal Armed Forces according to decree BMVg-Org 1, Az 10-02-05 of 17 May 1989 (VMBl 1989, p. 189) (e. g. marketable standard applications software), industry is not committed to the development standard of the Federal Republic of Germany. This does not hold if special requirements with respect to security or quality exist.

    The application of the V-Model is not mandatory for the development of individual IT systems.

    For those IT enterprises under development or in use, decisions have to be made on a case-to-case basis.

    Based on the standard and by taking into consideration the individual IT environment, those in charge of the individual software development/SWMM installation of the Federal Armed Forces have to select and install tools. These tools must be combined into software development environments (SDE) and it must be made sure that they meet the Functional Tool Requirements.

    In the long run, any software development environment already available in these installations must comply with the Functional Tool Requirements.

    When placing orders and/or utilizing the software development environment owned by the contractor it must be proven that the Functional Tool Requirements are met.

    When applying these regulations, the following standards must be adhered to:

    The publications of the Development Standard for IT Systems of the Federal Republic of Germany will be in the form of General Directives: The term "project" used in the V-Model has to be given the same meaning as the term "enterprise", which is usual in the Federal Armed Forces.

    The technical results generated while using the V-Model are integrated into the step-by-step decisions/phase documents, according to /AU 220/. The connection between V-Model and GD 220 is explained in Part 2 "Supplements with Regard to Authorities" of the General Directive No. 250 (not included in these html pages).

    IT portions as integrated parts of a weapon system have to be handled within the corresponding enterprise. The products that are generated for the IT portion according to the V-Model are integral parts of the whole enterprise.

    The General Directives are regulations and have to be treated, listed, and accounted for accordingly. They must be requested from the authority that is issuing these directives. Supplementary updates keep the contents up to date.

    Technical suggestions with regard to changes or additions have to be sent with the enclosed Change Request/Problem Report to

          BWB IT I 5
          Postfach 7360
          56057 Koblenz

    They are further processed in a change control procedure. For more information call BWB IT I 5.

    Previous Next GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster