Version 41.1 by wah on 2012/10/25 11:00
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 |=(((
12
13 )))|=(((
14 KIELER
15 )))|=(((
16 YAKINDU
17 )))|=(((
18
19 )))
20 |(((
21 Transition
22 )))|(((
23 [[image:attach:image2012-10-11 13:46:43.png]]
24 )))|(((
25 [[image:attach:image2012-10-11 13:46:50.png]]
26 )))|(((
27 **YAKINDU**: There is only one type for transitions
28
29 **KIELER**: Strong Abort, Week Abort, Normal Termination
30 )))
31 |(((
32 State
33 )))|(((
34 [[image:attach:image2012-10-11 13:47:11.png]]
35 )))|(((
36 [[image:attach:image2012-10-11 13:49:10.png]]
37 )))|(((
38
39 )))
40 |(((
41 Composite State
42 )))|(((
43 [[image:attach:image2012-10-11 13:47:20.png]]
44 )))|(((
45 [[image:attach:image2012-10-11 13:47:58.png]]
46 )))|(((
47
48 )))
49 |(((
50 Initial State
51 )))|(((
52 [[image:attach:image2012-10-15 14:41:10.png]][[image:attach:image2012-10-11 13:46:58.png]]
53 )))|(((
54 [[image:attach:image2012-10-11 13:52:3.png]]
55 )))|(((
56 **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.
57
58 (% style="color: rgb(0,0,0);" %)**KIELER**: Initial states are supposed to have a thicker border than normal states
59 )))
60 |(((
61 Final State
62 )))|(((
63 [[image:attach:image2012-10-15 14:40:31.png]][[image:attach:image2012-10-11 13:47:5.png]]
64 )))|(((
65 [[image:attach:image2012-10-11 13:51:43.png]]
66 )))|(((
67 **YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State
68
69 **KIELER**: Final states are depicted with a double border
70 )))
71 |(((
72 History
73 )))|(((
74 [[image:attach:image2012-10-11 13:47:27.png]][[image:attach:image2012-10-11 13:47:32.png]]
75 )))|(((
76 [[image:attach:image2012-10-11 13:47:54.png]]
77 )))|(((
78 **YAKINDU**:
79
80 * Shallow History: (% style="color: rgb(0,0,0);" %)is a pseudo state. It is placed inside a region of a composite state.
81 * (% 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.-
82
83 **KIELER**: A History is a attribute of a Transition
84 )))
85 |(((
86 Synchronization
87 )))|(((
88
89 )))|(((
90 [[image:attach:image2012-10-11 13:47:49.png]]
91 )))|(((
92 **YAKINDU**: Synchronization is a pseudo state.
93
94 **KIELER**: Synchronization not needed in KIELER
95
96 *
97 ** No interlevel transitions
98 ** Closest construct: normal termination
99 )))
100 |(((
101 Choice
102 )))|(((
103 [[image:attach:image2012-10-11 13:47:38.png]]
104 )))|(((
105 [[image:attach:image2012-10-11 13:47:44.png]]
106 )))|(((
107
108 )))
109
110 |=(((
111
112 )))|=(((
113 KIELER
114 )))|=(((
115 YAKINDU
116 )))
117 |(((
118 Interface declaration
119 )))|(((
120 [[image:attach:image2012-10-12 10:59:54.png]]
121 )))|(((
122 [[image:attach:image2012-10-12 10:51:52.png]]
123 )))
124
125 = Yakindu SCT module structure =
126
127 [[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"]]
128
129 = Customizing Yakindu SCT Editor to SyncCharts =
130
131 Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax:
132
133 * adapting the graphical representation (sgraph + ui)
134 * extending or replacing the textual description language (stext)
135
136
137
138 (% style="margin-left: 30.0px;" %)
139 == Adapting the graphical representation ==
140
141 (% style="margin-left: 30.0px;" %)
142 (% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several steps are required:(%%)
143 (% style="color: rgb(0,0,0);" %)
144
145
146
147 *
148 *1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\
149 *11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]]
150 *11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]]
151 \\
152 *1. Figures (org.yakindu.sct.ui.editor.editor.figures)
153 \\
154 *1. Editparts (org.yakindu.sct.ui.editor.editparts)
155 \\
156 *1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets)
157 \\
158 *1. The palette (org.yakindu.sct.ui.editor/plugin.xml)
159
160 (% style="margin-left: 60.0px;" %)
161
162 Examples:
163
164 * [[How to modify Initial and Finial States in Yakindu SCT Editor>>doc:How to modify Initial and Final States in Yakindu SCT Editor]]
165 * [[doc:How to add Transition Types in Yakindu SCT Editor]]
166
167 (% style="margin-left: 30.0px;" %)
168 == Extending or replacing the textual description language ==
169
170 (% style="margin-left: 30.0px;" %)
171 (% style="color: rgb(0,0,0);" %)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. It is case sensitive.

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage