Changes between Version 23 and Version 24 of Archtectural Overview Design Principles


Ignore:
Timestamp:
Sep 9, 2007, 7:53:35 PM (17 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Design Principles

    v23 v24  
    73734.2 Separation of Responsibilities
    7474
    75 openEHRで使われている第2の重要な設計パラダイムはコンピュータ環境における責任の分離である。複雑なドメインは機能性が関心の及ぶ広い範囲でまず切り分けられたときにのみ扱うことができる
     75openEHRで使われている第2の重要な設計パラダイムはコンピュータ環境における責任の分離である。複雑なドメインは機能性が関心の及ぶ広い範囲(例えば「システムの中のシステム」)を最初に切り分けることができたときにだけ扱うことができる[[FootNote(Maier M. Architecting Principles for Systems-of-Systems. Technical Report, University of Alabama in Huntsville. 2000. Available at http://www.infoed.com/Open/PAPERS/systems.htm)]]
    7676
    7777A second key design paradigm used in openEHR is that of separation of responsibilities within the computing environment. Complex domains are only tractable if the functionality is first partitioned into broad areas of interest, i.e. into a "system of systems" [6]. This principle has been understood in computer science for a long time under the rubrics "low coupling", "encapsulation" and "componentisation", and has resulted in highly successful frameworks and standards, including the OMG's CORBA specifications and the explosion of object-oriented languages, libraries and frameworks. Each area of functionality forms a focal point for a set of models formally describing that area, which, taken together usually correspond to a distinct information system or service.