|T.4 Deletion Conditions|
|Activities and Results||Supporting
|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.
||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.
||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.
||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.
||Activity cannot be deleted. A reference to the executing organization unit can be added.
|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.|
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.
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.
|This page online GDPA Online Last Updated 03.Mar.2004 by C. Freericks|