NOTE:
This documentation is intended for modelers who use the Statecharts languages. The documentation for language engineers using or extending the Statecharts language is located here.

Statecharts are a comfortable language to describe behavior based on the internal state of a component. Statecharts have originally been invented and described in [Harel'87] and were given a sound semantical basis. They extend automata theory in various forms, including hierarchy, actions, etc. Statecharts are the foundational behavior description during which for modeling standards, such as UML and SysML.

Dependent on the application domain, several forms of Statecharts are needed for example to accommodate stimuli in form of method calls, incoming values (signals) or only preconditions that trigger certain forms of actions.

• doc contains images used for the documentation of the language
• src/test/resources/examples contains exemplary Statecharts models
• src/main/grammars contains language components provided for statecharts
• detailed language description for language developers

Here is a small teaser for the UML Statechart language, which allows a method call as stimulus, Java expressions as constraints and Java blocks/statements as actions:

statechart Door {
  state Opened [9 < now < 18];  // state with invariant
  initial state Closed;
  state Locked;
                                // transitions 
  Opened -> Closed  close() ;
  Closed -> Opened  open()    / { count++; ringTheDoorBell(); };
  Closed -> Locked  timeOut() / lockDoor(); ;
  Locked -> Closed  [isAuthorized() && keyFits()] unlock() ;
}

This example models the three states of a door: Opened, Closed, and Locked and four transitions (each terminated by ;).

• States may be marked with initial and final.
• A transition is defined by source -> target states, a stimulus, such as a method call close(), a trigger condition [...], and an action / ....
• Expressions can be used for conditions, and statements respectively blocks {...} for the actions.

Further language concepts of the UML Statechart are shown in the following example, where state EngineRunning has two substates as well as entry, exit actions and an invariant:

statechart Car {
  initial state EngineOff;
  state EngineRunning [!fuelIsEmpty] {  // state with substates and state invariant (Boolean expression)
    entry / {lightsOn(); }              // entry / exit action
    exit  / {lightsOff();}
    initial state Parking;              // substates
    state Driving;
  };
}

Expressions and statements are taken from MontiCores basic grammar library and can be extended by any own interesting language constructs (such as sending or receiving messages !m or ?m)

Further example models such as Door.sc or Car.sc can be found here: src/test/resources/examples.

Graphical representations of the examples above:

Figure 2: Graphical Representation of the Door Statechart.

Figure 3: Graphical Representation of the Car Statechart.

• Download UML Statecharts Tool

Alternatively, the tools can be built from source code.

This section explains how to build and set up the command line interface tools for the SC languages from the source code of the tool. Alternatively, the tool can be downloaded.

To build the project, it is required to install a Java 8 JDK and git.

git clone <link to this Git repository>
cd sc-language

gradle build --refresh-dependencies

• The jars of the tools are now available in target/libs.
• A report of executed tests of the tool is found in target/reports/tests/test/index.html.
• Example generation results can be found in target/gentest* directories.

The StatechartsTool offers options for processing Statechart models. It provides through the CLI as follows:

java -jar MCStatecharts.jar [-h] -i <fileName> [-path <p>] [-pp [<file>]] [-s [<file>]]

where the arguments are:

exemplary usage:

  java -jar MCStatecharts.jar -h
  java -jar MCStatecharts.jar -i Car.sc -pp
  java -jar MCStatecharts.jar -i DoorExample.sc -gen myDoors 

The statechart language project also comes with a model transformations engine based on MontiTrans. It supports defining transformations utilizing the concrete syntax of the language for a more intuitive mapping of model elements. Look here for further information.

Please make sure that

• your complete workspace only uses UNIX line endings (LF)
• all files are UTF-8 without BOM and
• you use 2 spaces indentation for all files (no tabs)
• On Windows: configure git to not automatically replace LF with CRLF during checkout:
  git config --global core.autocrlf input

• Project root: MontiCore @github
• MontiCore documentation
• List of languages
• MontiCore Core Grammar Library
• Best Practices
• Publications about MBSE and MontiCore
• Licence definition