Previous Next Functional Tool Requirements Homepage  
Project Management Submodel  
SPM01 - Managing Project Resources  

  LPM01 - Projektressourcen verwaltens

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.5 - Generation of Preliminary Plan

  • Project Plan.Resource Plan

    • PM4 - Detailed Planning

  • Project Plan.Resource Plan

    • PM11 - Supplying Resources

  • Making Resources available

    • Method

    none

    2 Brief Characteristics

    This service unit defines the requirements for tools that are project-specifically applied

    When administering available resources, among other things, information to resources are initialized, changed on request, and deleted.

    3 Requirements

    3.1 Requirements for Interfaces

    SPM01.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.
    SPM01.I.2 Output interface to SPM02 - Supporting Planning of the Project Organization It is possible to transmit information about resources without further transformation via the object management to SPM02 in order to generate project organization plans.
    SPM01.I.3 Output interface to SPM04 - Supporting Planning of the Project Realization It is possible to transmit information about resources without further transformation via the object management to SPM04 in order to generate project realization plans.
    SPM01.I.4 Output interface to SPM05 - Supporting Cost Estimation It is possible to transmit information about resource groups without further transformation via the object management to SPM05 in order to be used for the cost estimation.

    3.2 Requirements for the Methods Support

    none

    3.3 Requirements for Functions

    SPM01.F.1 Input of resources It is possible to collect resources.
    SPM01.F.2 Resource groups It is possible to collect resource groups or to combine existing resources into groups.
    SPM01.F.3 Information to resources
    SPM01.F.3.1 Free text It is possible to collect free text descriptions for resources.
    SPM01.F.3.2 Identifiers It is possible to allocate identifiers to resources (unique names).
    SPM01.F.3.3 Attributes It is possible to put attributes on resources used for evaluations.
    SPM01.F.3.4 Groups It is possible to allocate resources to groups.
    SPM01.F.3.5 V-Model roles It is possible to allocate the V-Model roles to resources.
    In this case, resources are the staff members in a project.
    SPM01.F.4 Resource classification
    SPM01.F.4.1 Resources not being subject to consumption It is possible to classify resources as "not being subject to consumption".
    This class of resources includes the staff members.
    SPM01.F.4.2 Resources being subject to consumption It is possible to classify resources as "being subject to consumption".
    This class of resources includes materials.
    SPM01.F.5 Resource types
    SPM01.F.5.1 Resource type staff It is possible to define resources of the type staff.
    SPM01.F.5.2 Resource type hardware/software It is possible to define resources of the type hardware/software.
    SPM01.F.5.3 Resource type material It is possible to define resources of the type material.
    SPM01.F.6 Resource allocation It is possible to allocate resources to the activities of the Project Manual.
    This is realized by placing a Work Order.
    SPM01.F.7 Measuring units
    SPM01.F.7.1 Time-oriented It is possible to define time-oriented measuring units.
    Time-oriented measuring units are: year, month, week, calendar day, working day, hours, minutes.
    SPM01.F.7.2 Quantity-oriented It is possible to define quantity-oriented measuring units.
    For resource type material, the measuring unit is to be the number or piece.
    SPM01.F.7.3 Value-oriented It is possible to define scales of charges (costs) for the resource usage.
    SPM01.F.8 Calendar
    SPM01.F.8.1 Input of calendars It is possible to enter individual calendars for projects and staff members.
    SPM01.F.8.2 Availability It is possible to define the availability of resources either linear or non-linear over the time.
    SPM01.F.8.3 Hierarchical calendars The calendars for resources and projects have a hierarchical relationship.
    The calendar scheduling (e. g. holidays, vacation with regard to country, company, and staff member) are inherited in the hierarchy.
    SPM01.F.8.4 Assignment of priorities It is possible to assign priorities to calendars.
    The hierarchy of the calendar can be overwritten by means of a priority.
    SPM01.F.9 Date information It is not possible to enter invalid date information.

    3.4 Other Requirements

    SPM01.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.
    SPM01.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.
    SPM01.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