Previous Next V-Model Official Homepage by IABG  
Header  
PM 4: Detailed Planning  

  PM4 - Feinplanung

Contents  
  • Product Flow
  • Handling
  • Recommendation
  • Explanation
  •  
  • Roles
  • Methods
  • Tools Requirements
  • External Norms
  • Product Flow

    From Product to Methods Tool Req. Ext. Norms
    Activity State Chapter Title Activity State
    SD2 being proc./
    accepted
    All System Architecture - -     /ISO IEC 12207/

    Supply Proc.:
    Exec. and Control,

    Devlp. Proc.:
    Proc. Implement.,

    Doc. Proc.:
    Proc. Implement.,

    Mngmt. Proc.:
    Planning,

    Infraest. Proc.:
    Establ. of the Infraestr.,

    Training Proc.:
    Proc. Implem.

    PM1 accepted All Project Manual - -    
    PM3
    PM6
    PM8
    - All Report Documents:
    Protocol
    Progress Report
    Final Project Report
    Case Report
    Memo
    Internal Message
    Invitation
    - -    
    - - All Product CM2 planned    
    PM1 being proc. All Project Plan PM3
    PM4
    PM6
    PM7
    PM8
    PM10
    PM11
    PM12
    PM14
    CM4
    being proc. (1) BAR (2)
    EMOD
    NPT (2)
    TREE
    SPM01
    SPM04
    SPM05

    + "Chapter" are extra columns from the original printed version of GD 250

    Handling

    The goal of this activity is to realize the next planning section (one or several main activities or subactivities) on the basis of the existing preliminary planning (activity PM1.5 - Generation of Preliminary Plan) and to generate detailed planning by taking into consideration the specifications in the Project Manual.

    Detailed planning requires the following steps:

    * Technical Tailoring

    Based on the preliminary planning, it must be decided if in this actual case an activity or product that has been stated in the Project Manual will make sense or not (activity and product instantiation). This leads to a definition of the granularity of activities (e. g. activities will be dropped or combined) and the updating of the product structure (in case some chapters are dropped).

    This activity must be carried out prior to the realization of an activity or the generation of a product.

    For this, all technical deletion conditions contained in the Project Manual, chapter Overview, are applied to the activity under discussion or to the product. If the condition with regard to an activity or product has been fulfilled the corresponding activity/product or product chapter may be dropped.

    Activities or products for which no technical deletion conditions have been defined or for which deletion conditions have not been fulfilled must be realized or generated, respectively.

    When generating a product it must be observed that for chapters for which respective deletion conditions have been fulfilled and which can therefore be dropped, the chapter headings and the chapter numbers shall be kept. The reason for deleting the chapter will then replace the chapter text.

    * Planning Product Structure and Proces Organization

    It is to be planned which new products have to be generated in the following development section. These products must be added to the product structure plan, if not yet done.

    Concerning activities of the next planning section, it must be decided who will take over which tasks-and when-and which dependencies among them will exist (process organization). CM and PM activities are only planned, if the general information laid down in the CM Plan or Project Manual are not sufficient. Planning of QA activities takes place in the Assessment Plan. As soon as new products are planned, they have to be passed on for configuration identification (the product is allocated the state "planned").

    * Effort Planning and Time Scheduling

    Based on the existing preliminary planning, efforts and deadlines have to be determined for all planned activties. The criticality/methods matrix, which demands a higher generation and assessment effort for high criticality products, has an impact on this planning.

    Depending on the experience of the risk management, the preliminary planning must be modified.

    * Resource Planning

    For any activities and products-resulting from the technical tailoring-detailed resource planning is required. This includes the infrastructure necessary to realize the tasks, hardware, system software, tools and devices.

    * Planning Baselines

    According to the project development, further baselines must be defined. For products within a baseline that are subject to dynamic processing (refinement or adding of statements) the planned processing status of the corresponding products within the baseline must be established.

    * Subprojects/Subcontracts

    If allowed according to the corresponding contract it is possible to allocate subcontracts. This requires the setting up of subprojects with exactly defined task descriptions (products to be generated, activities to be realized). Negotiations with eligible subcontractors are to be initiated; finally a contract must be drawn up and signed together with the chosen partner (activity PM2 - Placement/ Procurement). Thus, a part of the system is separated, allocated to external contractors, and developed in parallel. The supervision that terms of contract are fulfilled is realized in activity PM3 - Contractor Management. The same holds for setting up internal subprojects. For this, subproject leaders will be appointed which together with their own team will develop a separate complex, thereby acting independently; organizationally, however, they are subordinate to the project management of the overall project.

    Recommendation

    The detailed planning should start from the SD (main) activities; based on this the related QA and CM activities ought to be planned.

    Explanation

    Classifying a System and its functional units with regard to criticality and security has an impact on detailed planning. The measures, products, methods, and tools required for the corresponding evaluation level have to be taken into consideration. If necessary, Change Requests/Problem Report must be written for the Project Manual and the QA Plan.

    Roles

    Role Participation
    Project Leader responsible
    Project Administrator cooperating

    Methods

    Product Methods Allocation Use
    Chapter 2.1
    Project Plan.
    Product Structure Plan
    TREE - Tree Diagram Generate
    Chapter 2.2
    Project Plan.
    Process Organization
    NPT - Network Planning Technique Generate
    Chapter 3.1.1
    Project Plan.
    Efforts (Planned and Actual) for SD/QA/CM/PM Activities
    EMOD - Estimation Models Generate
    Chapter 3.1.2
    Project Plan.
    Deadlines (Planned and Actual) for SD/QA/CM/PM Activities
    BAR - Bar Plan Generate
    Chapter 3.1.3
    Project Plan.
    Milestone Plan
    BAR - Bar Plan Generate
    Chapter 3.1.6
    Project Plan.
    Delivery and Supply Deadlines
    BAR - Bar Plan Generate
    Chapter 3.2.1
    Project Plan.
    Planned Values
    BAR - Bar Plan (2) Generate
    EMOD - Estimation Models Generate
    NPT - Network Planning Technique (2) Generate
    Chapter 4.1
    Project Plan.
    Staff
    BAR - Bar Plan Generate
    Chapter 4.2
    Project Plan.
    Resources
    BAR - Bar Plan Generate

    Tools Requirements

    Product Functional Tools Requirements
    Project Plan.Resource Plan SPM01 - Managing Project Resources
    Project Plan.Project Realization
    Project Plan.Efforts Plan and Time Schedule
    Project Plan.Resource Plan
    SPM04 - Supporting Planning of the Project Realization
    Project Plan.Efforts Plan and Time Schedule SPM05 - Supporting Cost Estimation

    External Norms

    Norm Process Chapter Obs.
    /ISO IEC 12207/ Supply Process Execution and Control (s. Part 3 - ISO 3.2.1)
    Development Process Process Implementation (s. Part 3 - ISO 3.2.1)
    Documentation Process Process Implementation (s. Part 3 - ISO 3.2.2)
    Management Process Planning (s. Part 3 - ISO 3.2.3)
    Infraestructure Process Establishment of the Infraestructure (s. Part 3 - ISO 3.2.3)
    Training Process Process Implementation (s. Part 3 - ISO 3.2.3)


    Note:

    (1) The state "b. proc." merely reflects the CM aspect. The authorization of the Project Plan by the project management responsible is nevertheless required, possibly with the participation of the QA representative.

    (2) Method BAR is to be applied if no complex arrangement relations and logical interdependences exist during the detailed planning; otherwise method NPT has to be applied.

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