Summary

• Page properties (3 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+KIELER.Discontinued Projects.Actor Oriented Modeling (KAOM).WebHome

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.sgu
	1	+XWiki.cds

Content

...	...	@@ -1,4 +1,8 @@
1		-{{panel title="Project Overview" borderStyle="dashed"}}
	1	+{{note title="Legacy Project"}}
	2	+KAOM is not maintained anymore and hence not part of any KIELER release.
	3	+{{/note}}
	4	+
	5	+{{panel borderStyle="dashed" title="Project Overview"}}
2	2	Responsible:
3	3
4	4	* [[Miro Spönemann>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/msp/||shape="rect"]]
...	...	@@ -81,7 +81,7 @@
81	81	=== (% lang="en" class="short_text hps" %)Special case(%%): ===
82	82
83	83	(% class="hps" lang="en" %)
84		-It is possible to force data flows in contrary to the general specifications . This is particularly the case when there are multiple top-level actors. The specification of data flows between these actors is set to the specifications of other data flows. For the specification, all predecessors of the actor and the actor itself, which define the source and target, must be specified by IDs. For the specification the path to the source and to the destination must be specified. Both are separated by a right-leaning arrow. A path consists of the ID of the source (or destination) and the ID of the actor, in which it is defined, and the IDs of all textual comprehensive actors. The ID of the defining actors is placed in front of the ID of the source (or destination) and separated by a colon. The IDs of the textual comprehensive actors, are arranged in descending order, placed in front of the ID of the defining actor. (% lang="en" class="hps" %)The IDs(% lang="en" %) (% class="hps" %)of all(%%) (%%)actors(% lang="en" %) (%%)in the path are (% lang="en" class="hps hps" %) (% class="hps" lang="en" %) separated from each other by an underscore q(%%). Source and destination can differ in more than one hierarchical level. All characters that are replaced with underscores in an ID must also be replaced with underscores in the specifying.
	88	+It is possible to force data flows in contrary to the general specifications . This is particularly the case when there are multiple top-level actors. The specification of data flows between these actors is set to the specifications of other data flows. For the specification, all predecessors of the actor and the actor itself, which define the source and target, must be specified by IDs. For the specification the path to the source and to the destination must be specified. Both are separated by a right-leaning arrow. A path consists of the ID of the source (or destination) and the ID of the actor, in which it is defined, and the IDs of all textual comprehensive actors. The ID of the defining actors is placed in front of the ID of the source (or destination) and separated by a colon. The IDs of the textual comprehensive actors, are arranged in descending order, placed in front of the ID of the defining actor. (% lang="en" class="hps" %)The IDs(% lang="en" %) (% class="hps" %)of all(%%) (%%)actors(% lang="en" %) (%%)in the path are(% lang="en" class="hps hps" %) (% class="hps" lang="en" %) separated from each other by an underscore (%%). Source and destination can differ in more than one hierarchical level. All characters that are replaced with underscores in an ID must also be replaced with underscores in the specifying.
85	85
86	86	{{code title="example for specifying a special data flow"}}
87	87	link: source -> ID0_ID1_ID2_..._ID:target, ... ;

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-1998871
	1	+885110

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1998871/C2DF
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/885110/C2DF