Boundary Model
|
Term |
Boundary Model |
|
Aliases |
- |
Definition
A Boundary Model defines the logical connection structure through which information and deliverables are exchanged across different processes or layers—such as knowledge modeling, process style, and execution architecture. It bridges the internal and external aspects of a development method, clarifying inputs, outputs, and dependencies.
SimpleModeling
In SimpleModeling, the Boundary Model is a key structural element surrounding the development method. It imports outputs from knowledge modeling as inputs, and exports the results of the development method to the process style and execution architecture. Through this mechanism, it establishes an integrated framework connecting the model-driven, knowledge-driven, and AI-assisted layers.
Relation to boundary object
A Boundary Model is composed of multiple Boundary Objects. While a boundary object represents an individual data structure or artifact, the boundary model serves as a structural schema that organizes and contextualizes them. When defining inputs and outputs of a development method, these boundary objects form the concrete interface elements.
Reference Relations
| 関連概念 | 分類 | 説明 |
|---|---|---|
|
Boundary Object |
一般理論(Star & Griesemer, 1989)+ SimpleModeling拡張 |
異なる領域間の共有・協働を媒介する個別の成果物。SimpleModelingでは「プロセス間接続の最小単位」として再定義。 |
|
Boundary Class |
UML / OOAD 用語 |
外部アクターと内部システムを接続するクラス。構造的には類似するが、モデル全体の論理接続を扱う点で境界モデルとは異なる。 |
|
System Boundary |
システム理論・情報システム工学 |
システムの内外を区分する概念。SimpleModelingではこの「境界」の考えを発展させ、モデル間連携構造へと拡張。 |
Remarks
This concept is inspired by Star & Griesemer’s “Boundary Object” theory and reconstructed in SimpleModeling as a design structure for process interoperability. Thus, it extends beyond conventional UML or systems theory, becoming part of the meta-development structure that integrates development methods, knowledge modeling, and architecture.