Previous Next V-Model Official Homepage by IABG  
CM Homepage  
8.4.4 Project History (PHis)  

  Projekthistorie

Contents  
  • Introduction
  • Document Index
  • Document Structure
  • Links to the V-Model Mailinglist
  • Introduction

    The development and change history of the System are documented in the Project History. It is used as a source of information and reference about the course of the project, and, by maintaining static plan and change data, also as a planning and controlling instrument.

    Document Index

    1. General Information
    2. Course of the Development
          2.1. Decisions
          2.2. Difficulties, their Causes and Elimination
    3. Change/Version History
          3.1. Traceability of Changes
          3.2. Documentation of the Change History
          3.3. Documentation of the Change Decisions
    4. Planning Statistics
          4.1. Deviations from the Plan
          4.2. Plan Changes
          4.3. Analysis of Causes
          4.4. Possibilities to Prevent further Deviations from the Plan
    5. Change and Error Statistics
          5.1. Change Request/Problem Report, Change Proposal, Change Order, Change Memo
          5.2. Products Affected
          5.3. Classification and Judgment
          5.4. Diagnosis/Cause
          5.5. Measures
    6. Analysis/Evaluation of the Project History

    Document Structure

    1. General Information

    See schema 1. General Information.

    2. Course of the Development

    2. 1. Decisions

    All decisions determining the further project development both technically and administrationally have to be justified.

    2. 2. Difficulties, their Causes and Elimination

    Difficulties occurring during project development must be documented, together with the causes (if known), the effects and the measures taken to eliminate them.

    3. Change/Version History

    The change/version history wants to make the content, the causes, the decisions and the change development between successive product versions traceable during the entire operation time of the project, and also for the entire System.

    3. 1. Traceability of Changes

    This chapter describes the information about traceability of changes (documentation of changes from one version to the next, and documentation stating which changes have been integrated into which version).

    3. 2. Documentation of the Change History

    All of the Change Request/Problem Reports made available have to be documented with the resulting Change Proposals and Change Orders, i. e. in their individual status.

    3. 3. Documentation of the Change Decisions

    It is necessary to document a reason for the decision (permission, postponement or rejection) about each Change Request/Problem Report.

    4. Planning Statistics

    The planning statistics documents for which items the Project Plan was changed when, by whom, and why. The following information has to be included:

    4. 1. Deviations from the Plan

    Planned/actual deviations from the Project Plan must be stated.

    4. 2. Plan Changes

    If plan changes resulted in delivery problems, new requests of customer, etc. they have to be stated.

    4. 3. Analysis of Causes

    The analysis results of the above listed deviations from the plan and of the plan changes have to be stated.

    4. 4. Possibilities to Prevent further Deviations from the Plan

    This chapter documents measures to prevent further deviations from plan and delays of the final deadline, based on the analyses of causes.

    5. Change and Error Statistics

    5. 1. Change Request/Problem Report, Change Proposal, Change Order, Change Memo

    The number of Change Request/Problem Reports, Change Proposals, Change Orders, and Change Memos that were generated during the project are listed in the form of a statistics.

    5. 2. Products Affected

    All products affected by changes are listed. In this connection, it is necessary to differentiate between those products that are directly affected by a change, and those products that only have to be changed as a consequence of the actual change.

    5. 3. Classification and Judgment

    The above listed Change Request/Problem Reports, Change Proposals and Change Orders are classified and judged on the basis of the type of error and on the frequency this error occurs.

    5. 4. Diagnosis/Cause

    The causes for the Change Request/Problem Reports are classified and edited in a statistical form. This is used as the basis for the recommendation of measures.

    5. 5. Measures

    Measures for the future prevention of every class of errors are deviated from the diagnosis/cause investigation.

    6. Analysis/Evaluation of the Project History

    Based on the analysis and evaluation of the Project History it is possible to get empirical experience and knowledge about the development process of the project that will be useful as lessons learned for future projects.

    Links to the V-Model Mailinglist

    Mail 0250 - Re: Erfahrungsberichte (250)
    Mail 0237 - Re: Ein paar Fragen zum V-Modell (237)
    Mail 0229 - Ein paar Fragen zum V-Modell (229)

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