Wiki source code of A SyncChart-Editor based on Yakindu

Version 33.1 by wah on 2012/10/16 11:49

version	line-number	content
7.1	1	= Yakindu SCT =
	2
8.1	3	YAKINDU Statechart Tools (SCT) is an open source tool for the specification and development of reactive, event-based systems using state machines.
5.1	4
8.1	5	It 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
5.1	7	[[image:attach:Yakindu SCT.png]]
9.1	8
12.1	9	= Yakindu SCT Editor VS KIELER SyncCharts Editor =
10.1	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	)))\|(((
11.1	27	YAKINDU: There is only one type for transitions
	28
	29	KIELER: Strong Abort, Week Abort, Normal Termination
10.1	30	)))
	31	\|(((
29.1	32	State
10.1	33	)))\|(((
29.1	34	[[image:attach:image2012-10-11 13:47:11.png]]
10.1	35	)))\|(((
29.1	36	[[image:attach:image2012-10-11 13:49:10.png]]
10.1	37	)))\|(((
29.1	38
10.1	39	)))
	40	\|(((
29.1	41	Composite State
10.1	42	)))\|(((
29.1	43	[[image:attach:image2012-10-11 13:47:20.png]]
10.1	44	)))\|(((
29.1	45	[[image:attach:image2012-10-11 13:47:58.png]]
10.1	46	)))\|(((
29.1	47
10.1	48	)))
	49	\|(((
29.1	50	Initial State
10.1	51	)))\|(((
29.1	52	[[image:attach:image2012-10-15 14:41:10.png]][[image:attach:image2012-10-11 13:46:58.png]]
10.1	53	)))\|(((
29.1	54	[[image:attach:image2012-10-11 13:52:3.png]]
10.1	55	)))\|(((
29.1	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.
30.1	57
31.1	58	(% style="color: rgb(0,0,0);" %)KIELER: Initial states are supposed to have a thicker border than normal states
10.1	59	)))
	60	\|(((
29.1	61	Final State
10.1	62	)))\|(((
29.1	63	[[image:attach:image2012-10-15 14:40:31.png]][[image:attach:image2012-10-11 13:47:5.png]]
10.1	64	)))\|(((
29.1	65	[[image:attach:image2012-10-11 13:51:43.png]]
10.1	66	)))\|(((
29.1	67	YAKINDU: Final States are pseudo states. The Final State may not be a Composite State
30.1	68
	69	KIELER: Final states are depicted with a double border
10.1	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	)))\|(((
14.1	78	YAKINDU:
11.1	79
14.1	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
27.1	83	KIELER: A History is a attribute of a Transition
10.1	84	)))
	85	\|(((
	86	Synchronization
	87	)))\|(((
	88
	89	)))\|(((
	90	[[image:attach:image2012-10-11 13:47:49.png]]
	91	)))\|(((
	92
	93	)))
	94	\|(((
28.1	95	Choice
10.1	96	)))\|(((
	97	[[image:attach:image2012-10-11 13:47:38.png]]
	98	)))\|(((
	99	[[image:attach:image2012-10-11 13:47:44.png]]
	100	)))\|(((
	101
	102	)))
13.1	103
18.1	104	\|=(((
13.1	105
18.1	106	)))\|=(((
	107	KIELER
	108	)))\|=(((
	109	YAKINDU
	110	)))
	111	\|(((
	112	Interface declaration
	113	)))\|(((
	114	[[image:attach:image2012-10-12 10:59:54.png]]
	115	)))\|(((
	116	[[image:attach:image2012-10-12 10:51:52.png]]
	117	)))
13.1	118
21.1	119	= Yakindu SCT module structure =
18.1	120
21.1	121	[[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"]]
	122
16.1	123	= Customizing Yakindu SCT Editor to SyncCharts =
	124
	125	Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax:
	126
	127	* adapting the graphical representation (sgraph)
	128	* extending or replacing the textual description language (stext)
	129
19.1	130	1. (((
23.1	131	== Adapting the graphical representation ==
19.1	132
25.1	133	(% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several step is required:(%%)
	134	(% style="color: rgb(0,0,0);" %) (%%)\\
	135
	136	1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\
	137	11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]]
	138	11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]]
	139	\\
	140	1. Figures (org.yakindu.sct.ui.editor.editor.figures)
	141	\\
	142	1. Editparts (org.yakindu.sct.ui.editor.editparts)
	143	\\
	144	1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets)
26.1	145	\\
	146	1. The palette (org.yakindu.sct.ui.editor/plugin.xml)
32.1	147	)))
	148
	149	(% style="margin-left: 60.0px;" %)
	150
33.1	151	Example: [[How to modify Initial and Finial States in Yakindu SCT Editor>>doc:How to modify Initial and Final States in Yakindu SCT Editor]]
26.1	152	\\
32.1	153
20.1	154	1. (((
23.1	155	== Extending or replacing the textual description language ==
20.1	156
	157	(% 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.
	158	)))

Wiki source code of A SyncChart-Editor based on Yakindu

Navigation

Quick Links