Previous Next V-Model Official Homepage by IABG  
Part 3: Collection of Manuals Homepage  
Tailoring  Homepage  
T.4 Deletion Conditions  

  T.4 Streichbedingungen

Contents  
  • T.4.1 Preliminaries
  • T.4.2 Conventions
  • T.4.3 Deletion of Activities
  • T.4.4 Deletion of Products
  • T.4.1 Preliminaries

    A deletion condition consists of the following information: Next, the general effects of deletions are listed. A deletion condition may be used both for the tender-relevant tailoring (BT) and for the technical tailoring (TT). The following table illustrates the effects for activities. Similar effects can be observed for products.

    Activities and Results Supporting
    Tailoring Method
    Effects/Notes
    An activity is not required for the project. BT Activity is to be deleted by mention of the reason. Information generated by the activity (products or sub-products) are not relevant; they are to be deleted.
    An activity is generally required for the project. However, it may be deleted during project realization under certain circumstances. TT Activity may be deleted during project realization, reasons are to be given. The information created by the activity (products or sub-products) are not relevant; they are to be deleted.
    The results of an activity are required for the project and can be adopted completely, both with regard to format and content, from a preceding project. BT, TT The activity is to be deleted. The available results are adopted. Products come from "outside".
    The results of an activity are required for the project and can be adopted completely, in a very large parts, from a preceding project. BT, TT The activity can be deleted, with reference to required adjustment. Only small adjustments are expected.
    An activity is required for the project. However, it is handled "outside" the project. none Activity cannot be deleted. A reference to the executing organization unit can be added.

    Table T.22: Deletion Condition Preliminaries

    T.4.2 Conventions

    The deletion conditions are listed in tabular form. The two first columns refer to the relevance of the deletion condition for one of the tailoring methods. If "-" entries in columns BT or TT are available it means that the activity shall be deleted according to the tailoring method.

    BT TT Activity/Reason for Deletion Effects
    - - Activity Activity must not be deleted.
    Activity Activity can be deleted in BT and TT.
    - Activity Activity can be deleted in BT.
    - Activity Activity can be deleted in TT.

    Table T.23: Deletion Condition Conventions

    In the following handling of deletion conditions, the standard chapter 1 General Information is not separately listed for products. This chapter is always relevant when the product or one of its chapters has to be generated.

    Product chapters are omitted when the sub-activities they were generated by are deleted.

    T.4.3 Deletion of Activities

    An activity can be deleted when the reason for the deletion is given. The deletion condition examples listed next have to be-if applicable-classified as BT or TT deletion condition with regard to the project. Further individual deletion reasons must be updated, if necessary. If no deletion conditions are listed for the activities, this does not necessarily mean they cannot be deleted. A project-specific reason must be given for each deletion.

    The deletion conditions also apply the features and quantifications that are introduced in section T.3.1 Characteristics with Corresponding Quantifications. They are listed along with the submodels project management, quality assurance, and system development.

    In this connection, the list of deletion reasons must be interpreted as "or" conditions.

    T.4.3.1 Submodel PM

    T.4.3.2 Submodel QA

    T.4.3.3 Submodel CM

    T.4.3.4 Submodel SD

    T.4.4 Deletion of Products

    (Access next html pages)

    Previous Next This page online  •  GDPA Online  •  Last Updated 03.Mar.2004 by C. Freericks