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.stu230980

Content

...	...	@@ -1,9 +1,12 @@
1		-{{panel title="Project Overview" borderStyle="dashed"}}
	1	+{{info title="Legacy Project"}}
	2	+KAOM is not maintained anymore and hence not part of any KIELER release.
	3	+{{/info}}
	4	+
	5	+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"]]
5	5	* Sven Gundlach
6		-{{/panel}}
7	7
8	8	== Introduction ==
9	9
...	...	@@ -13,7 +13,7 @@
13	13
14	14	To work with C2DF you must pass as the first source and a destination directory as an argument. C2DF generates then in the target directory for each annotated source file from the source directory or a subdirectory thereof a //.KAOT//-file. Also, a subdirectory called //xml// will be created in the target directory. This have to be deleted.
15	15
16		-=== (% lang="en" class="short_text hps alt-edited" %)General description(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)of annotations(% class="short_text" lang="en" %):(%%) ===
	19	+=== (% class="alt-edited hps short_text" lang="en" %)General description(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)of annotations(% class="short_text" lang="en" %):(%%) ===
17	17
18	18	(% class="short_text" lang="en" %) (%%)To declare annotations, you need to put in a C-comment before the annotated object. This comment will be initiated by ///*// and completed with //*///. Before the start  of each content must be written the keyword //@kaom//. Then follow the individual contents.
19	19
...	...	@@ -35,7 +35,7 @@
35	35	*/
36	36	{{/code}}
37	37
38		-=== (% lang="en" class="short_text hps" %)Specification(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)of inputs(% class="short_text" lang="en" %):(%%) ===
	41	+=== (% class="hps short_text" lang="en" %)Specification(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)of inputs(% class="short_text" lang="en" %):(%%) ===
39	39
40	40	The specification of the inputs of an actor must be initiated by the keyword //input~://. Then follows the list of inputs. Each entry must have a unique ID in the actor. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all inputs must be terminated with a semicolon.
41	41
...	...	@@ -43,26 +43,26 @@
43	43	input: ID_1 "label", ID_2 "label", ... ;
44	44	{{/code}}
45	45
46		-=== (% lang="en" class="short_text hps" %)Specification(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)of outputs(% class="short_text" lang="en" %):(%%) ===
	49	+=== (% class="hps short_text" lang="en" %)Specification(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)of outputs(% class="short_text" lang="en" %):(%%) ===
47	47
48		-The specification of the (% lang="en" class="short_text hps" %)outputs(% class="short_text" lang="en" %) (%%) of an actor must be initiated by the keyword //output~://. Then follows the list of outputs. Each entry must have a unique ID in the actor. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all outputs must be terminated with a semicolon.
	51	+The specification of the (% class="hps short_text" lang="en" %)outputs(% class="short_text" lang="en" %) (%%) of an actor must be initiated by the keyword //output~://. Then follows the list of outputs. Each entry must have a unique ID in the actor. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all outputs must be terminated with a semicolon.
49	49
50	50	{{code title="example for specifying outputs"}}
51	51	output: ID_1 "label", ID_2 "label", ... ;
52	52	{{/code}}
53	53
54		-=== (% lang="en" class="short_text hps" %)Specification(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)of (% class="short_text" lang="en" %)data flows:(%%) ===
	57	+=== (% class="hps short_text" lang="en" %)Specification(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)of (% class="short_text" lang="en" %)data flows:(%%) ===
55	55
56	56	(% lang="en" %)
57		-(% lang="en" class="short_text hps" %)The specification of the(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)data(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)flows of an(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)actor must be(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)initiated by the keyword(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)//link~://.(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %) Then follows the list of the(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)data flows.(%%) The ID of the source and the ID of the target must be specified for each entry. Source and destination are separated by a right-leaning arrow indicating the direction of data flow. If source or destination are defined in another actor as the data flow, then the ID of the actor of the source or destination must be specified. The ID of the actor is placed directly in front of the ID of the source or target, separated by a dot. Actors, in which source and destination are defined, may not differ by more than one hierarchical level. Other entries are separated with commas. The list of all data flows must be terminated with a semicolon.
	60	+(% class="hps short_text" lang="en" %)The specification of the(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)data(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)flows of an(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)actor must be(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)initiated by the keyword(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)//link~://.(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %) Then follows the list of the(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)data flows.(%%) The ID of the source and the ID of the target must be specified for each entry. Source and destination are separated by a right-leaning arrow indicating the direction of data flow. If source or destination are defined in another actor as the data flow, then the ID of the actor of the source or destination must be specified. The ID of the actor is placed directly in front of the ID of the source or target, separated by a dot. Actors, in which source and destination are defined, may not differ by more than one hierarchical level. Other entries are separated with commas. The list of all data flows must be terminated with a semicolon.
58	58
59	59	{{code title="example for specifying data flows"}}
60	60	link: source -> context.target, context.source -> context.target, source -> target, ... ;
61	61	{{/code}}
62	62
63		-=== (% lang="en" class="short_text hps" %)Specification(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)of (% class="short_text" lang="en" %)included actors:(%%) ===
	66	+=== (% class="hps short_text" lang="en" %)Specification(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)of (% class="short_text" lang="en" %)included actors:(%%) ===
64	64
65		-(% lang="en" class="short_text hps short_text hps" %)The specification of the(% class="short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps" %)included actors of an(% class="short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps" %)actor must be(% class="short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps" %)initiated by the keyword(% class="short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps" %)//content~://.(% class="short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps" %) Followed by the list of the included actors. Each entry must be specified with the name of its (%%)represented(% lang="en" class="short_text hps short_text hps" %) function in the source code. Followed by a unique ID within the actor, which is separated from the function name with a colon. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all(% class="short_text hps short_text hps short_text hps short_text" lang="en" %) (% lang="en" class="short_text hps short_text hps short_text hps short_text hps" %)included actors(% lang="en" class="short_text hps short_text hps" %) must be terminated with a semicolon.
	68	+(% class="hps hps short_text short_text" lang="en" %)The specification of the(% class="hps short_text short_text" lang="en" %) (% class="hps hps short_text short_text" lang="en" %)included actors of an(% class="hps short_text short_text" lang="en" %) (% class="hps hps short_text short_text" lang="en" %)actor must be(% class="hps short_text short_text" lang="en" %) (% class="hps hps short_text short_text" lang="en" %)initiated by the keyword(% class="hps short_text short_text" lang="en" %) (% class="hps hps short_text short_text" lang="en" %)//content~://.(% class="hps short_text short_text" lang="en" %) (% class="hps hps short_text short_text" lang="en" %) Followed by the list of the included actors. Each entry must be specified with the name of its (%%)represented(% class="hps hps short_text short_text" lang="en" %) function in the source code. Followed by a unique ID within the actor, which is separated from the function name with a colon. Optional behind the ID can be any label in quotation marks. Other entries are separated with commas. The list of all(% class="hps hps hps short_text short_text short_text short_text" lang="en" %) (% class="hps hps hps hps short_text short_text short_text short_text" lang="en" %)included actors(% class="hps hps short_text short_text" lang="en" %) must be terminated with a semicolon.
66	66
67	67	{{code title="example for specifying included actors"}}
68	68	content: function_1:ID "label", function_2:ID "label", ... ;
...	...	@@ -70,7 +70,7 @@
70	70
71	71	(% class="almost_half_cell" %)
72	72	(((
73		-=== (% lang="en" class="short_text hps" %)Specifying(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)top-level(% class="short_text" lang="en" %) (% lang="en" class="short_text hps" %)actors(% class="short_text" lang="en" %):(%%) ===
	76	+=== (% class="hps short_text" lang="en" %)Specifying(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)top-level(% class="short_text" lang="en" %) (% class="hps short_text" lang="en" %)actors(% class="short_text" lang="en" %):(%%) ===
74	74
75	75	The specification of the top-level actors of a data flow diagram must be initiated by the keyword //toplevel~://. The specification must be placed in the annotation of the represented function. The entry consists of an unique ID in the actor. Optional behind the ID can be any label in quotation marks. The entry must be terminated with a semicolon.
76	76
...	...	@@ -78,10 +78,10 @@
78	78	toplevel:ID "label";
79	79	{{/code}}
80	80
81		-=== (% lang="en" class="short_text hps" %)Special case(%%): ===
	84	+=== (% class="hps short_text" lang="en" %)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 (%%). 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.
	87	+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. (% class="hps" lang="en" %)The IDs(% lang="en" %) (% class="hps" %)of all(%%) actors(% lang="en" %) (%%)in the path are(% class="hps hps" lang="en" %) (% 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		-7700635
	1	+885110

URL

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