https://www.eclipse.org/sirius/doc/specifier/general/Specifying_Viewpoints.html
SiriusはVSMを使ってコンフィグレーション。構造、外観、振舞いを記述するモデル。
■viewpoint
定義のコアになる要素(representation specification とrepresentation extension specification)
■representation
ドメインデータのグラフィカルな構造のグループ。
Siriusは4種類(ダイアグラム、テーブル、マトリクス、テーブル、ツリー)
■mapping
ドメインデータのマッピング
■style
外観のスタイル。形や色などの
■Tool
ツールが無いと、単なる表示だけになる。
ツールは、要素の生成/削除、編集をユーザが行えるようにする。
ツールは振舞いを記述するためのマッピング
The main concepts you will work with as a specifier are:
Viewpoint A viewpoint is one of the core elements that a specifier defines: it is a logical set of representation specifications and representation extension specifications.
Representation A representation is a group of graphical construction which represent domain data. A representation describes the structure, appearance and behavior of your modelers. By default, Sirius supports four kinds of representations (called dialects): diagrams, tables, matrices (aka cross-tables), and trees. All follow the same basic principles in their definitions.
Mapping A mapping identifies a sub-set of the semantic model’s element that should appear in a representation and indicates how they should be represented. Each dialect offers different kinds of mappings. For example, diagrams provide container mappings, which can be used to represent semantic elements with graphical containers, where other elements (specified by other mappings) can appear. A mapping exists inside the Viewpoint Specification Model, but on a concrete representation it will produce instances. If you specify a container mapping to represent, say, divisions in an enterprise, and the model of your enterprise contains four divisions, a concrete diagram will show four containers, each an instance of the same mapping, but associated to a different semantic element.
Style Each mapping can have one or several styles associated to it, which are used to configure the visual appearance of the elements they represent. For example, for diagram elements this would include their shape and colors.
Tool Without tools, your representations would be only visualizations, with no edition capabilities. While this can be sometimes useful, most representations will allow users to create, edit and delete elements. Tools are associated to mappings to describe their behaviors. Each kind of user interaction supported by Sirius (e.g. creation or deletion, label editing, edge reconnection...) is specified by a different kind of tool, but they all follow the same principles in their definition.
Viewpoint A viewpoint is one of the core elements that a specifier defines: it is a logical set of representation specifications and representation extension specifications.
Representation A representation is a group of graphical construction which represent domain data. A representation describes the structure, appearance and behavior of your modelers. By default, Sirius supports four kinds of representations (called dialects): diagrams, tables, matrices (aka cross-tables), and trees. All follow the same basic principles in their definitions.
Mapping A mapping identifies a sub-set of the semantic model’s element that should appear in a representation and indicates how they should be represented. Each dialect offers different kinds of mappings. For example, diagrams provide container mappings, which can be used to represent semantic elements with graphical containers, where other elements (specified by other mappings) can appear. A mapping exists inside the Viewpoint Specification Model, but on a concrete representation it will produce instances. If you specify a container mapping to represent, say, divisions in an enterprise, and the model of your enterprise contains four divisions, a concrete diagram will show four containers, each an instance of the same mapping, but associated to a different semantic element.
Style Each mapping can have one or several styles associated to it, which are used to configure the visual appearance of the elements they represent. For example, for diagram elements this would include their shape and colors.
Tool Without tools, your representations would be only visualizations, with no edition capabilities. While this can be sometimes useful, most representations will allow users to create, edit and delete elements. Tools are associated to mappings to describe their behaviors. Each kind of user interaction supported by Sirius (e.g. creation or deletion, label editing, edge reconnection...) is specified by a different kind of tool, but they all follow the same principles in their definition.
Cross Tables are slightly different from edition tables. They are optimized to represent relationship between elements in a matrix-like way. Both lines and columns represent elements, and each call at an intersection if a certain relationship exists between them. Cross tables also support sub-lines, but not sub-columns. However provided the right tools are specified, users can create and/or delete columns in addition to lines.
Cross tables are specified using a Cross Table Description element, which works exactly like Edition Table Description elements. The differences appear in the type of elements they can contain.
CrossTableは通常のテーブルとは異なる。
CrossTableはマトリクス的な関係を示す。
ラインとカラムの両方を要素として、示す。
intersection
Cross Tables are slightly different from edition tables. They are optimized to represent relationship between elements in a matrix-like way. Both lines and columns represent elements, and each call at an intersection if a certain relationship exists between them. Cross tables also support sub-lines, but not sub-columns. However provided the right tools are specified, users can create and/or delete columns in addition to lines.
Cross tables are specified using a Cross Table Description element, which works exactly like Edition Table Description elements. The differences appear in the type of elements they can contain.
CrossTableは通常のテーブルとは異なる。
CrossTableはマトリクス的な関係を示す。
ラインとカラムの両方を要素として、示す。
intersection