||The objective of the Software Lifecycle Process Model /VM 1997/, also known as V-Model, is to regulate the software development process within the German federal administration. V-Model determines an uniform and binding set of activities and products (results) that are required during the software development (SD) and the accompanying activities for Quality Assurance (QA), Configuration Management (CM) and technical Project Management (PM).
The complete V-Model standard comprises three books:
1. General Directive - GD 250 - Lifecycle process model
This book is conformed by three parts:
- Part 1 - Regulations Describes, in 141 pages, the activities and products that are required during the software development and maintenance and modification.
- Part 2 - Supplement with Regard to Authorities(Not included in the Process Web Center)
- Part 3 - Collection of Manuals. It is composed by the following 12 Manuals (245 pages):
- FAO - Meeting the Minimum IT Requirements of the Federal Audit Office by Means of the V-Model (14 pages)
- BPR - The Connection between Business Process Reengineering and the V-Model (6 pages)
- HW - Hardware Generation (11 pages)
- ISO - The V-Model in an ISO and AQAP Environment (26 pages)
- OOL - Consideration of Object-Oriented Languages (8 pages)
- R- Concept of Roles in the V-Model (16 pages)
- RE - Reverse Engineering (51 pages)
- SEC - Application of the V-Model and ITSEC (7 pages)
- SA - Safety and Criticality (8 pages)
- SC - Scenarios (34 pages)
- ENV - Co-ordinating the V-Model in its Environment (13 pages)
- T - Tailoring and Project-Specific V-Model (49 pages)
2. General Directive - GD 251 - Methods Allocation
[Methods 1997]. (282 pages)
- Description of the methods: (141 pages)
- Annex 1: Explanations (93 pages)
- Annex 2: Collection of Manuals (48 pages)
3. General Directive - GD 252 - Functional Tool Requirements
[Tools 1997]. (341 pages)
The Process Web Center entails the V-Model standard (GD 250, GD 251 and GD 252), version 97, without considering the "Part 2 - Supplement with Regard to Authorities" of the GD 250, consists of 1009 pages for the English version and circa another 1009 pages for the German version, resulting in a total of 2018 printed pages.
- Functional Tool Requirements (304 pages)
- Annex 1: Explanations (37 pages)
The V-Model is available in the following different formats:
- Word 95 format - The 3 complete books in English and German are provided by IAGB for downloading at http://www.v-modell.iabg.de/vm97.htm.
- Windows help format - The 3 complete books in German are distributed by ANSTAND in 2 CD's. Requests at: http://www.ansstand.de/
- Postscript format - The 3 complete books in English and German are available for downloading in GDPA.
- Web-based format - V-Model guide [Becker-Kornsteat 1999] provides an on-line web-version of the part 1 of the book GD 250 in German. IABG provides an on-line version for the book GD 251 in German at http://www.v-modell.iabg.de/au251htm/index.htm . GDPA comprises the 3 complete books, in English and German for on-line use and for downloading.
The Process Web-Centre implemented in GDPA centralises, organises and stores information between the printed documents of V-Model [GD250], Methods Allocation [GD251] and Functional Tool Requirements [GD252], and the data contained in a local database such as product-flow, tailoring graphs, mails of the V-Model mailinglists, formal methods tools and processes, references to external norms, glossary, etc.
Figure Intro 6: GDPA integrates V-Model
Steps to start applying V-Model:
- Actually, the V-Model does not start on the activity SD 1. The first real step is the project setup. See the "Set-up" form page to check the main activities
- The second step comprehends the tailoring, i.e., the elimination of the activities from the complete set provided in the V-Model which are not necessary to the specific project. V-Model provides a "pre-tailoring" schema. See pre-tailoring forms to check the main options. After the pre-tailoring, starts the tailoring itself. See the session Tailoring and Project-Specific V-Model from the V-Model.
- The third step is to assign the methods and tools to the remaining activities. See the sessions Methods Allocations and Functional Tool Requirements.
- The last step correspond to the project management: assign durations, roles, resources, etc.