Skip to Content

Changes for page Kieler Compiler

Last modified by Richard Kreissig on 2023/09/14 10:52
From version 19.1
edited by cmot
on 2014/03/21 12:18
Change comment: There is no comment for this version
To version 29.1
edited by Alexander Schulz-Rosengarten
on 2018/11/22 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cmot
1 +XWiki.als
Content
... ... @@ -1,4 +1,8 @@
1 -{{panel title="Project Overview" borderStyle="dashed"}}
1 +{{panel bgColor="orange" title="Deprecated since 0.12"}}
2 +This article is deprecated. The described features are no longer available in current releases.
3 +{{/panel}}
4 +
5 +{{panel borderStyle="dashed" title="Project Overview"}}
2 2  Responsible:
3 3  
4 4  * [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]], [[Steven Smyth>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/ssm/||shape="rect"]]
... ... @@ -6,11 +6,13 @@
6 6  Related Theses:
7 7  
8 8  * none yet
13 +
14 +**To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>doc:Online Compiler]].**
9 9  {{/panel}}
10 10  
11 11  = Kieler Compiler (KiCo) =
12 12  
13 -In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent.
19 +In order to integrate and be able to evaluate our compiler chain from SCCharts to C or VHDL code we use the KiCo project as a generic framework that allows to register setp-by-step transformations on EObjects. These can then be handled by the generic KIEM KiCo DataComponent. **To see the KielerCompiler in action, we provide an Online SCCharts Compiler [[here>>url:http://www.sccharts.com/||shape="rect"]].**
14 14  
15 15  
16 16  
... ... @@ -20,11 +20,18 @@
20 20  
21 21  The KIELER Compiler (KiCo) project allows to register step-by-step model transformations on EObjects that could be written in Xtend or Java. These transformations are registered using an extension point provided (see below). After registering transformations these can be used by simply call the KielerCompiler compilation method as also explained further below.
22 22  
29 +(% class="wrapped" %)
23 23  |=(((
24 -[[image:attach:KiCo.jpg]]
31 +(% class="content-wrapper" %)
32 +(((
33 +[[image:attach:IMAG4642.jpg]]
34 +)))
25 25  )))|=(((
26 -[[image:attach:KiCo3.jpg]]
36 +(% class="content-wrapper" %)
37 +(((
38 +[[image:attach:KiCo.jpg]]
27 27  )))
40 +)))
28 28  
29 29  == Extension Point ==
30 30  
... ... @@ -35,13 +35,13 @@
35 35  
36 36  {{{de.cau.cs.kieler.kico}}}
37 37  
38 -
51 +\\
39 39  )))
40 40  1. Add the extension
41 41  
42 42  
43 43  {{{de.cau.cs.kieler.kico.transformation}}}(((
44 -
57 +\\
45 45  )))
46 46  1. (((
47 47  Add one of the following extension element
... ... @@ -49,6 +49,7 @@
49 49  [[image:attach:KiCo2.jpg]]
50 50  )))
51 51  
65 +(% class="wrapped" %)
52 52  |=(((
53 53  Extension Element
54 54  )))|=(((
... ... @@ -96,9 +96,7 @@
96 96   dependencies="TRIGGEREFFECT, SURFACEDEPTH"
97 97   name="Transform All Normalize">
98 98   </transformationGroup>
99 - </extension>
100 - <extension
101 - point="de.cau.cs.kieler.kico.transformation">
113 +
102 102   <transformationMethod
103 103   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
104 104   id="TRIGGEREFFECT"
... ... @@ -105,10 +105,7 @@
105 105   method="transformTriggerEffect"
106 106   name="Transform Trigger and Effect">
107 107   </transformationMethod>
108 - </extension>
109 -
110 - <extension
111 - point="de.cau.cs.kieler.kico.transformation">
120 +
112 112   <transformationMethod
113 113   class="de.cau.cs.kieler.sccharts.extensions.SCChartsCoreTransformation"
114 114   id="SURFACEDEPTH"
... ... @@ -115,10 +115,7 @@
115 115   method="transformSurfaceDepth"
116 116   name="Transform Surface Depth">
117 117   </transformationMethod>
118 - </extension>
119 -
120 - <extension
121 - point="de.cau.cs.kieler.kico.transformation">
127 +
122 122   <transformationGroup
123 123   id="ALL"
124 124   dependencies="CORE NORMALIZE"
... ... @@ -127,12 +127,13 @@
127 127   </extension>
128 128  {{/code}}
129 129  
130 -
136 +\\
131 131  
132 132  == Compilation ==
133 133  
134 134  Once a bunch of model transformations are registered, these can simply be called using the KiCo central "KielerCompiler" class with its method compile(). This will be given a List<String> of transformation IDs or a comma separated String of transformation IDs as the first parameter. The second parameter is the EObject that is being transformed. It should meet the signature of the first model transformation called. Note that the actual model transformations that are done may vary because KiCo will automatically inspect the dependencies of each transformation requested (deep-recursively). If you do not like this to happen as an advanced user you can use a third parameter that will skip this autocompletion. Note that if you switch this off also NO transformation groups can be processed. Here is an overview and examples how to use the compile() method:
135 135  
142 +(% class="wrapped" %)
136 136  |=(((
137 137  Method
138 138  )))|=(((
... ... @@ -190,10 +190,153 @@
190 190  
191 191  {{/code}}
192 192  
200 +=== Requirement Completion ===
201 +
202 +\\
203 +
204 +(% class="wrapped" %)
205 +|=(((
206 +(% class="content-wrapper" %)
207 +(((
208 +(% style="text-align: center;" %)
209 +Original
210 +
211 +(% class="wrapped" %)
212 +|=(((
213 +(% class="content-wrapper" %)
214 +(((
215 + [[image:attach:dependencies2.jpg]]
216 +
217 +(% style="text-align: center;" %)
218 +Original Dependency
219 +Graph
220 +)))
221 +)))|=(((
222 +(% class="content-wrapper" %)
223 +(((
224 +(% style="text-align: center;" %)
225 +[[image:attach:dependencies3.jpg]]
226 +
227 +(% style="text-align: center;" %)
228 +Two alternative
229 +transformation
230 +implementations
231 +for Abort
232 +)))
233 +)))
234 +
235 +\\
236 +)))
237 +)))|=(((
238 +(% class="content-wrapper" %)
239 +(((
240 +(% style="text-align: center;" %)
241 +Example 1
242 +
243 +(% class="wrapped" %)
244 +|=(((
245 +(% class="content-wrapper" %)
246 +(((
247 + [[image:attach:dependencies4.jpg]]
248 +
249 +(% style="text-align: center;" %)
250 +Selected for
251 +transformation
252 +)))
253 +)))|=(((
254 +(% class="content-wrapper" %)
255 +(((
256 + [[image:attach:dependencies4b.jpg]]
257 +
258 +(% style="text-align: center;" %)
259 +Auto selected
260 +requirements
261 +)))
262 +)))
263 +
264 +\\
265 +)))
266 +)))
267 +
268 +\\
269 +
270 +\\
271 +
272 +(% class="wrapped" %)
273 +|=(((
274 +(% class="content-wrapper" %)
275 +(((
276 +(% style="text-align: center;" %)
277 +Example 2
278 +
279 +(% class="wrapped" %)
280 +|=(((
281 +(% class="content-wrapper" %)
282 +(((
283 +[[image:attach:dependencies5.jpg]]
284 +
285 +(% style="text-align: center;" %)
286 +Selected for
287 +transformation
288 +)))
289 +)))|=(% style="text-align: center;" %)(% style="text-align: center;" %)
290 +(((
291 +(% class="content-wrapper" %)
292 +(((
293 +[[image:attach:dependencies5b.jpg]]
294 +
295 +Auto selected
296 +requirements
297 +using DEFAULT
298 +of alternative
299 +group
300 +
301 +\\
302 +)))
303 +)))
304 +
305 +\\
306 +)))
307 +)))|=(((
308 +(% class="content-wrapper" %)
309 +(((
310 +(% style="text-align: center;" %)
311 +Example 3
312 +
313 +(% class="wrapped" %)
314 +|=(((
315 +(% class="content-wrapper" %)
316 +(((
317 +[[image:attach:dependencies6.jpg]]
318 +
319 +(% style="text-align: center;" %)
320 +Selected for
321 +transformation
322 +)))
323 +)))|=(((
324 +(% class="content-wrapper" %)
325 +(((
326 +[[image:attach:dependencies6b.jpg]]
327 +
328 +(% style="text-align: center;" %)
329 +Auto selected
330 +requirements
331 +using selected
332 +alternative
333 +)))
334 +)))
335 +
336 +\\
337 +)))
338 +)))
339 +
340 +\\
341 +
193 193  == Help / Problems / FAQs ==
194 194  
195 195  Maybe you get into problems when using KiCo. The following list should give you hints to solve these. If you have a problem not considered here please write us an e-mail (see above for contact information of the persons in charge of KiCo).
196 196  
346 +(% class="wrapped" %)
197 197  |=(((
198 198  Symptom
199 199  )))|=(((
... ... @@ -222,7 +222,7 @@
222 222  Maybe the plugin declaring "ABORT2" was not loaded
223 223  or the ID is misspelled.
224 224  
225 -
375 +\\
226 226  )))|(((
227 227  Check why "ABORT2" may not be found
228 228  by KiCo, more specifically, check if the
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -9470111
1 +50823276
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/9470111/Kieler Compiler
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/50823276/Kieler Compiler