Previous Next V-Model Official Homepage by IABG  
Part 3: Collection of Manuals Homepage  
Tailoring  Homepage  
T.4.3.1 Submodel PM  

  T.4.3.1 Submodell PM

BT TT Activity Reason for Deletion Effects
- - PM1 - Project Initialization   
- - PM1.1 - Setting up the Project   
PM1.2 - Definition of Project Criteria and Development Strategy
  • This is a SWMM project and the project description is available.
  • The information in chapter Project Manual.Project Description is specified.
    - PM1.3 - Generation of Project-Specific V-Model
  • Project-specific V-model can be adopted from similar project (same characteristics).
  • The information in chapter Project Manual.Overview and Project Manual.Project-Specific V-Model are specified.
    PM1.4 - Toolset Management
  • This is a SWMM project and the Project Manual for development projects is available.
  • SDE, methods and standards are adopted from similar project (same characteristics).
  • SDE, methods and standards are specified by the customer.
  • The information in chapter Project Manual.Selection of Methods and Tools and Project Manual.Standards and Regulations is specified.
    - - PM1.5 - Generation of Preliminary Plan   
    - PM2 - Placement/ Procurement
  • No products/services are to be procured for the project.
  • The products "Tender Documents", "Tender", "Tender Evaluation" and "Contract" are omitted.
    - PM3 - Contractor Management
  • This is a project without the participation of contractors.
  • The relationshipt to contractors is defined, delays and conflicts are not expected. Thus the coordination of customers is realized within the scope of project control.
  • -
    - - PM4 - Detailed Planning
  • This is a small project where a plan (preliminary plan) is only generated once. The plan is obligatory for the entire development and will not be updated.
  •   
    PM5 - Cost/Benefit Analysis
  • This is a project where the solution suggested is binding.
  • There are no financial limitations with regard to development and application of the System.
  • Product Cost/Benefit Analysis is omitted.
    PM6 - Phase Review
  • The element to be developed (System, Segment, etc.) has no criticality and only low maintenance requirements.
  • In activities with low development risk the QA measures are sufficient.
  • -
    PM7 - Risk Management
  • The project management has enough experience to detect risks during project development and to introduce measures for detailed planning.
  • Only low restrictive actual state specifications (cost, deadlines, finances) exist.
  • This is a small or medium project without recognizable development risks.
  • Risks can almost always be prevented with sufficient experience and know-how.
  • Chapter Project Plan.Risk Considerations is omitted.
    - - PM8 - Project Control   
    PM9 - Information Service/Reporting
  • Development results of other submodels are used as case report.
  • -
    PM10 - Training/Instruction
  • The project is a maintenance/modification (SWMM) project and is implemented by the development team.
  • The project members have sufficient experience/knowledge with regard to the technology and the problems in connection with applications.
  • -
    PM11 - Supplying Resources
  • The project is a SWMM project and the infrastructure is available.
  • In comparison to the last activity realized, the resources are the same.
  • -
    PM12 - Allocation of Work Orders
  • This is a project with only few staff members (small/medium project).
  • Product Work Order is omitted.
    PM13 - Staff Training
  • Staff members have sufficient experience and know-how to execute the activities.
  • Missing information is made available with the work order.
  • Activity PM12 must not be deleted.
    - - PM14 - Project Completion   

    Table T.24: Deletion of Activities for Submodel PM

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