Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

 

Project Overview

Responsible:

Formerly Responsible / Previous Projects:

Related Theses:

  • Mirko Wischer, Textuelle Darstellung und strukturbasiertes Editieren von Statecharts, February 2006 (pdf)
  • Özgün Bayramoglu, KIELER Infrastructure for Textual Modeling, December 2009 (pdf)
  • Christian Schneider, Integrating Graphical and Textual Modeling, February 2011 (pdf)

 

SCCharts are typically modeled using the textual SCT language defined as an Xtext grammar in KIELER. Generally, if you do not know which elements can be placed at a certain cursor position you are assisted by a content-assist that can be called pressing <Ctrl>+<Space>. It will display all possible valid elements also considering scoping of variables.

 

In the following we will describe the basic elements using the famous ABRO example:

scchart ABRO {
  input bool A;
  input bool B;
  input bool R;
  output bool O = false;
  region Main:
  initial state ABO {
    initial state WaitAB {
      region HandleA:
      initial state WA
      --> DA with A;
      final state DA;
      region HandleB:
      initial state WB
      --> DB with B;
      final state DB;
    }
    >-> Done with / O = true;
    state Done;
  }
  o-> ABO with R;
}            
  1. In the first line you see how an SCChart is defined using the scchart keyword where the ID of the SCChart will be ABRO. An optional label can be inserted after ABRO using "<LABEL>".
  2. In the next three lines variables are declared, namely, A, B, R and O, where O is initialized with the value false. A, B, and R are inputs which must not be initialized and get there valued from the environment.
  3. An SCChart typically contains concurrent regions which are introduced with the keyword region as shown in Line 6.
  • No labels