The following table depicts a detailed comparison of the graphical representation between the KIELER SyncCharts Editor and the Yakindu SCT Editor.

 

KIELER

YAKINDU

 

Transition

image2012-10-11 13:46:43.png

image2012-10-11 13:46:50.png

YAKINDU: There is only one type for transitions

KIELER: Strong Abort, Week Abort, Normal Termination

State

image2012-10-11 13:47:11.png

image2012-10-11 13:49:10.png

 

Composite State

image2012-10-11 13:47:20.png

image2012-10-11 13:47:58.png

 

Initial State

image2012-10-15 14:41:10.pngimage2012-10-11 13:46:58.png

image2012-10-11 13:52:3.png

YAKINDU: Initials State are pseudo states. The Initial State may not be a Composite State. An initial state can only have one outgoing transition and no incoming.

KIELER: Initial states are supposed to have a thicker border than normal states

Final State

image2012-10-15 14:40:31.pngimage2012-10-11 13:47:5.png

image2012-10-11 13:51:43.png

YAKINDU: Final States are pseudo states. The Final State may not be a Composite State

KIELER: Final states are depicted with a double border

History

image2012-10-11 13:47:27.pngimage2012-10-11 13:47:32.png

image2012-10-11 13:47:54.png

YAKINDU:

  • Shallow History: is a pseudo state. It is placed inside a region of a composite state.
  • Deep History:  is similar to shallow history. With a deep history the latest state of multiple nested states is remembered.-

KIELER: A History is a attribute of a Transition

Synchronization

 

image2012-11-1 21:54:51.png

YAKINDU: Synchronization is a pseudo state.

KIELER: Synchronization not needed in KIELER


    • No interlevel transitions
    • Closest construct: normal termination

Choice

image2012-10-11 13:47:38.png

image2012-10-11 13:47:44.png

 

 

KIELER

YAKINDU

Interface declaration

image2012-10-12 10:59:54.png

image2012-10-12 10:51:52.png

Tags: