Previous Next Functional Tool Requirements Homepage  
Project Management Submodel  
SPM06 - Supporting Project Control and Steering  

  LPM06 - Projektkontrolle und -steuerung 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

    PM8 - Project Control

  • Report Documents

    • CM4.7 - Recording Project History

  • Project History.Planning Statistics

    • Method

    EVT - Earned Value Method
    TRDA - Trend Analysis

    2 Brief Characteristics

    This service unit defines the requirements for tools applied to compare planned data and actual data with regard to cost, schedules, and capacity loading. This may be realized both on explicit request or schedule- or event-driven.

    3 Requirements

    3.1 Requirements for Interfaces

    SPM06.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.
    SPM06.I.2 Input interface to SPM04 - Supporting Planning of the Project Realization It is possible to integrate project realization plans collected with SPM04 directly from the object management without further transformation for the project control and steering.
    SPM06.I.3 Input interface to SPM05 - Supporting Cost Estimation It is possible to integrate cost estimations collected with SPM05 without further transformation directly from the object management for the project control and steering.

    3.2 Requirements for the Methods Support

    SPM06.M.1 EVT - Earned Value Method
    SPM06.M.1.1 Earned value diagram It is possible to represent the development course of the monetary value for the actual performance, the actual cost, and the planned cost in form of an Earned Value Diagram.
    SPM06.M.2 TRDA - Trend Analysis
    SPM06.M.2.1 Trend curves
    SPM06.M.2.1.1 Effort It is possible to generate trend curves with regard to effort.
    SPM06.M.2.1.2 Schedule It is possible to generate trend curves with regard to schedule.

    3.3 Requirements for Functions

    SPM06.F.1 Evaluations Evaluations are possible for selectable sections from the database (e. g. referring to project, activity, resource).
    SPM06.F.2 Reports
    SPM06.F.2.1 Layout The report generator allows the definition of a uniform page layout.
    SPM06.F.2.2 Structure It is possible to freely define the content of the reports.
    SPM06.F.2.3 Addressees It is possible to generate reports from the database by taking into consideration the group of addressees.
    SPM06.F.2.4 Report period It is possible to select a time window. A time window limits the report to one report period.
    SPM06.F.3 Statistic evaluations
    SPM06.F.3.1 Evaluations per activity It is possible to realize statistic evaluations with regard to activities.
    SPM06.F.3.2 Evaluations per resource It is possible to realize statistic evaluations with regard to resources.
    SPM06.F.3.3 Evaluations per product It is possible to realize statistic evaluations with regard to products.
    SPM06.F.3.4 Evaluations for the total project It is possible to realize statistic evaluations with regard to the total project.
    SPM06.F.3.5 Evaluations for any time windows It is possible to realize statistical evaluations for any time windows.
    SPM06.F.4 Comparing plans It is possible to compare various plan versions.
    SPM06.F.5 Simulation It is possible to simulate different scenarios.
    SPM06.F.6 Missed deadlines It is possible to automatically display if deadlines have been missed.

    3.4 Other Requirements

    SPM06.O.1 Experience database It is possible to file planned and actual values in an experience database.
    SPM06.O.2 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.
    SPM06.O.3 Procedural command language The tool has a procedural command language that can be applied by the user to generate and run macros or procedures.
    SPM06.O.4 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