Version 44.1 by wah on 2012/10/31 13:02
Show last authors
1 = Yakindu SCT =
2
3 YAKINDU Statechart Tools (SCT) is an open source tool for the specification and development of reactive, event-based systems using state machines ([[Yakindu SCT User Guide>>attach:YAKINDU-SCT-UserGuide-1.2.0.pdf]]).
4
5 YAKINDU SCT consists of a graphical tool for editing and provides validation, simulation, and code generators for different target platforms. The tools are provided as Eclipse-plugins and integrate tightly into the IDE ([[Yakindu SCT Website>>url:http://www.itemis.de/itemis-ag/produkte/yakindu-open-source/yakindu-statechart-tools/language=de/43437/produktbeschreibung||shape="rect"]]).
6
7 [[image:attach:Yakindu SCT.png]]
8
9 = Yakindu SCT Editor VS KIELER SyncCharts Editor =
10
11 * Comparison of the graphical representation
12 * Comparison of the textual description language
13
14 |=(((
15
16 )))|=(((
17 KIELER
18 )))|=(((
19 YAKINDU
20 )))|=(((
21
22 )))
23 |(((
24 Transition
25 )))|(((
26 [[image:attach:image2012-10-11 13:46:43.png]]
27 )))|(((
28 [[image:attach:image2012-10-11 13:46:50.png]]
29 )))|(((
30 **YAKINDU**: There is only one type for transitions
31
32 **KIELER**: Strong Abort, Week Abort, Normal Termination
33 )))
34 |(((
35 State
36 )))|(((
37 [[image:attach:image2012-10-11 13:47:11.png]]
38 )))|(((
39 [[image:attach:image2012-10-11 13:49:10.png]]
40 )))|(((
41
42 )))
43 |(((
44 Composite State
45 )))|(((
46 [[image:attach:image2012-10-11 13:47:20.png]]
47 )))|(((
48 [[image:attach:image2012-10-11 13:47:58.png]]
49 )))|(((
50
51 )))
52 |(((
53 Initial State
54 )))|(((
55 [[image:attach:image2012-10-15 14:41:10.png]][[image:attach:image2012-10-11 13:46:58.png]]
56 )))|(((
57 [[image:attach:image2012-10-11 13:52:3.png]]
58 )))|(((
59 **YAKINDU**: Initials State are pseudo states. The Initial State may not be a Composite State. (% style="color: rgb(0,0,0);" %)An initial state can only have one outgoing transition and no incoming.
60
61 (% style="color: rgb(0,0,0);" %)**KIELER**: Initial states are supposed to have a thicker border than normal states
62 )))
63 |(((
64 Final State
65 )))|(((
66 [[image:attach:image2012-10-15 14:40:31.png]][[image:attach:image2012-10-11 13:47:5.png]]
67 )))|(((
68 [[image:attach:image2012-10-11 13:51:43.png]]
69 )))|(((
70 **YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State
71
72 **KIELER**: Final states are depicted with a double border
73 )))
74 |(((
75 History
76 )))|(((
77 [[image:attach:image2012-10-11 13:47:27.png]][[image:attach:image2012-10-11 13:47:32.png]]
78 )))|(((
79 [[image:attach:image2012-10-11 13:47:54.png]]
80 )))|(((
81 **YAKINDU**:
82
83 * Shallow History: (% style="color: rgb(0,0,0);" %)is a pseudo state. It is placed inside a region of a composite state.
84 * (% style="color: rgb(0,0,0);" %)Deep History: (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %) is similar to shallow history. With a deep history the latest state of multiple nested states is remembered.-
85
86 **KIELER**: A History is a attribute of a Transition
87 )))
88 |(((
89 Synchronization
90 )))|(((
91
92 )))|(((
93 [[image:attach:image2012-10-11 13:47:49.png]]
94 )))|(((
95 **YAKINDU**: Synchronization is a pseudo state.
96
97 **KIELER**: Synchronization not needed in KIELER
98
99 *
100 ** No interlevel transitions
101 ** Closest construct: normal termination
102 )))
103 |(((
104 Choice
105 )))|(((
106 [[image:attach:image2012-10-11 13:47:38.png]]
107 )))|(((
108 [[image:attach:image2012-10-11 13:47:44.png]]
109 )))|(((
110
111 )))
112
113 |=(((
114
115 )))|=(((
116 KIELER
117 )))|=(((
118 YAKINDU
119 )))
120 |(((
121 Interface declaration
122 )))|(((
123 [[image:attach:image2012-10-12 10:59:54.png]]
124 )))|(((
125 [[image:attach:image2012-10-12 10:51:52.png]]
126 )))
127
128 = Yakindu SCT module structure =
129
130 [[See Yakindu Wiki>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/developer/01_Overview/overview.html||shape="rect"]]
131
132 = Customizing Yakindu SCT Editor to SyncCharts =
133
134 Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax:
135
136 * adapting the graphical representation (sgraph + ui)
137 * extending or replacing the textual description language (stext)
138
139 (% style="margin-left: 30.0px;" %)
140 == Adapting the graphical representation ==
141
142 (% style="margin-left: 30.0px;" %)
143 (% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several steps are required:
144
145 *
146 *1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\
147 *11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]]
148 *11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]]
149 \\
150 *1. Figures (org.yakindu.sct.ui.editor.editor.figures)
151 \\
152 *1. Editparts (org.yakindu.sct.ui.editor.editparts)
153 \\
154 *1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets)
155 \\
156 *1. The palette (org.yakindu.sct.ui.editor/plugin.xml)
157
158 (% style="margin-left: 60.0px;" %)
159 **Examples:**
160
161 * [[How to modify Initial and Finial States in Yakindu SCT Editor>>doc:How to modify Initial and Final States in Yakindu SCT Editor]]
162 * [[doc:How to add Transition Types in Yakindu SCT Editor]]
163
164 (% style="margin-left: 30.0px;" %)
165 == Extending or replacing the textual description language ==
166
167 *
168 ** (% style="color: rgb(0,0,0);" %)Yakindu: The textual [[description language>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/user/05_Reference/reference.html#Statechartdescriptionlanguage||shape="rect"]] is used to declare and describe behaviors in the state machine.

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage