Changes between Version 13 and Version 14 of Archtectural Overview Versioning


Ignore:
Timestamp:
Oct 26, 2007, 2:32:26 PM (16 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Archtectural Overview Versioning

    v13 v14  
    7070
    7171構成管理の目的は以下について確実に行うことである
    72 
     72ssd.dyndns.info/Diary/
    7373The goal of configuration management is to ensure the following:
    7474
    … …  
    84848.3 Managing Changes in Time
    8585
    86 リポジトリを適切に変更管理するには2つの機構が必要である。第1に、バージョン制御
     86リポジトリを適切に変更管理するには2つの機構が必要である。第1に、バージョン制御はそれぞれの構成アイテムのバージョンとそれが一つであればディレクトリ構造も管理するために使用される。第2に、openEHRではcontributoinとして知られている「change-set」の概念である。ここの構成アイテムが
    8787
    8888Properly managing changes to the repository requires two mechanisms. The first, version control, is used to manage versions of each CI, and of the directory structure if there is one. The second is the concept of the "change-set", known as a contribution in openEHR. This is the set of changes to individual CIs (and other top-level structures in the EHR) made by a user as part of some logical change. For example, in a document repository, the logical change might be an update to a document that consists of multiple files (CIs). There is one Contribution, consisting of changes to the document file CIs, to the repository. In the EHR, a Contribution might consist of changes to more than one Composition, and possibly to the organising Folder structure. Any change to the EHR requires a Contribution. The kinds of changes that can occur to items affected in a Contribution are: