Previous Next Functional Tool Requirements Homepage  
Project Management Submodel  
SPM03 - Supporting Tender-Relevant Tailoring  

  LPM03 - Ausschreibungsrelevantes Tailoring unterstützen

Contents  
  • 1 Allocation to V-Model and Methods Allocation
  • 2 Brief Characteristics
  • 3 Requirements
  •       3.1 Requirements for Interfaces
  •       3.2 Requirements for the Methods Support
  •       3.3 Requirements for Functions
  •       3.4 Other Requirements
  • 1 Allocation to V-Model and Methods Allocation

    V-Model

    PM1.3 - Generation of Project-Specific V-Model

  • Project Manual.Project-Specific V-Model
  • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools that are project-specifically applied After answering questions about the contractual deletion conditions a project-specific V-Model will be generated. This function is referred to as "guided tailoring".

    Activity types of the internal V-Model structure can be deleted, independent of the deletion conditions. This function is referred to as "unguided tailoring".

    3 Requirements

    3.1 Requirements for Interfaces

    SPM03.I.1 Granularity The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface.
    SPM03.I.2 Output interface to SWFM01 - Workflow Management It is possible to transmit project-specific V-Models via the object management without further transformation to SWFM01 for the workflow management.
    SPM03.I.3 Output interface to SPM04 - Supporting Planning of the Project Realization It is possible to transmit project-specific V-Models via the object management without further transformation to SPM04 in order to generate project realization plans.
    SPM03.I.4 Output interface to SPM05 - Supporting Cost Estimation It is possible to transmit project-specific V-Models via the object management without further transformation to SPM05 in order to be used for the cost estimation.

    3.2 Requirements for the Methods Support

    none

    3.3 Requirements for Functions

    SPM03.F.1 Mapping the V-Model
    SPM03.F.1.1 Loading the V-Model It is possible to load the internal V-Model structure.
    The internal V-Model structure contains the activity types, the product types and the relationships between activity types and product types.
    SPM03.F.1.2 Contractual deletion conditions It is possible to load the contractual deletion conditions.
    SPM03.F.1.3 Technical deletion conditions It is possible to load the technical deletion conditions.
    SPM03.F.1.4 Loading the V-Model text It is possible to load the V-Model text, in particular the activity and product descriptions.
    SPM03.F.2 Generation of a project-specific V-Model
    SPM03.F.2.1 Sequentially Deletion conditions are sequentially answered by the user on screen.
    SPM03.F.2.2 New answers It is possible to return to already answered questions and to newly answer them.
    SPM03.F.2.3 Only relevant questions Questions that have been answered indirectly on the basis of a previous answer are no longer displayed.
    SPM03.F.2.4 Tailoring proposal After having walked through all project criteria in question, a Tailoring proposal is generated.
    Depending on the answers in the deletion conditions, certain activity types and possibly product types of the internal structure are already deleted in this proposal (or the product chapter is marked as "not relevant").
    SPM03.F.3 Deletion of activity types
    SPM03.F.3.1 Technical deletion conditions It is possible to define technical deletion conditions by which the realization of an activity is controlled.
    SPM03.F.3.2 Deletion of product types When deleting an activity type the product type resulting from this activity is automatically deleted or else the product chapter in question is marked as "not relevant".
    It is also possible that several product types or product chapters are affected by the deletion.
    SPM03.F.3.3 Deletion of (sub-) activity type After all subactivity types of a (sub-) activity type have been deleted, the (sub-) activity type will also be deleted.
    SPM03.F.3.4 Automatic deletion of subactivity types If an activity type is deleted, all its (optionally nested) subactivity types will be deleted as well.
    SPM03.F.3.5 Deletion of product type If an activity type is deleted, the generated product type is only deleted as well if the product is completely generated by this activity type.
    SPM03.F.3.6 Explicit deletion of activity types It is possible to delete activity types, independent of any deletion conditions.
    SPM03.F.4 Deletion of product types
    SPM03.F.4.1 Deletion of (sub-) product type After all subproduct types of a (sub-) product type have been deleted, the (sub-) product type will also be deleted.
    SPM03.F.4.2 Automatic deletion of subproduct types If a product type is deleted, all its (optionally nested) subproduct types will be deleted as well.
    SPM03.F.5 Changing activity descriptions
    SPM03.F.5.1 Deletions It is possible to delete non-applicable passages of the activity description.
    SPM03.F.5.2 Adjustments It is possible to modify the wording of the activity description.
    SPM03.F.5.3 Application information It is possible to add application information important for the course of the project to the activity description.
    SPM03.F.5.4 Original text
    SPM03.F.5.4.1 Changing passages The activity descriptions in the general V-Model consist of passages that can be modified and of passages that must not be changed.
    If a user attempts to modify a passage that must not be changed a message is displayed informing the user of this fact and the modification is not executed.
    SPM03.F.5.4.2 Marking changeable passages All text passages that can be changed have been marked.
    SPM03.F.5.5 Marking changed passages Changed text passages of activity description are automatically optically marked. Such a marking might be realized by using another font.
    SPM03.F.6 Storing and administering the V-Model
    SPM03.F.6.1 Development database The general V-Model is stored in the development database.
    SPM03.F.6.2 Several V-Models It is possible to administrate several project-specific V-Models simultaneously.
    This way, several projects can be handled simultaneously.

    3.4 Other Requirements

    SPM03.O.1 Upward compatibility It must be possible to process objects generated with an older release of the tool with the later release of that tool, without loss of information and functionality.
    SPM03.O.2 Procedural command language The tool has a procedural command language that can be applied by the user to generate and run macros or procedures.
    SPM03.O.3 Complexity There is no limitation of the complexity caused by the tool itself.

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