Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Henshin/Units

< Henshin
Revision as of 04:10, 6 March 2018 by Heidelme.students.uni-marburg.de (Talk | contribs) (Remove property 'Execution unsuccessful if')

In Henshin, control flow is specified using units. Units have a fixed number of sub-units, allowing for arbitrary nesting. This article describes the available units.

Usage

Unit creation in graphical editor

Create unit

To add a unit to a Henshin project in the graphical editor, first open the *.henshin_diagram file. Then select Unit from the Palette on the right of the window. Afterwards left-click any empty space of the Henshin diagram and choose the desired unit from the appearing menu.

Add sub-unit

If the selected unit is a Multi-Unit, some sub-units have to be added manually. Therefore select Invocation from the Palette and click on the according Multi-Unit. Then type the name of the desired rule or unit.

Unit creation in tree-based editor

To add a unit to a Henshin project in the tree-based editor, first open the *.henshin file. Then right-click on the parent Module. Select New Child and afterwards the desired unit from the context menu. After creation the units can be edited in their Properties view.

Henshin Units Creation TreeEditor.png

Multi-Units

Sequential Unit

Henshin Sequential Unit.png
  • Number of sub-units: arbitrary (0..*)
  • Available Flags/Properties: strict, rollback (both of type boolean)
  • Execution successful if:
    • strict=true: all sub-units successful
    • strict=false: at least one sub-unit successful or no sub-units existing
  • Control flow: The sub-units are executed in the given order.
    • strict=false, rollback=true/false: If one of the sub-units cannot be executed, the next sub-unit is executed.
    • strict=true, rollback=false: If one of the sub-units cannot be executed, the execution stops.
    • strict=true, rollback=true: If one of the sub-units cannot be executed, the execution stops and previous executions are reverted.

Priority Unit

Henshin Priority Unit.png
  • Number of sub-units: arbitrary (0..*)
  • Available Flags/Properties: none
  • Execution successful if: one sub-unit successful
  • Control flow: The sub-units are checked in the given order for executability. The first sub-unit found to be executable is executed.

Independent Unit

Henshin Independent Unit.png
  • Number of sub-units: arbitrary (0..*)
  • Available Flags/Properties: none
  • Execution successful: one sub-unit succesful
  • Control flow: The sub-units are checked in nondeterministic order for executability. The first sub-unit found to be executable is executed.

Unary Units

Loop Unit

Henshin Loop Unit.png
  • Number of sub-units: 1
  • Available Flags/Properties: none
  • Execution successful: always
  • Control flow: The sub-unit is executed as often as it is executable.

Iterated Unit

Henshin Iterated Unit.png
  • Number of sub-units: 1
  • Available Flags/Properties: iterations (integer), strict, rollback (both of type boolean)
  • Execution successful if:
    • strict=true: all iterations successful
    • strict=false: at least one iteration successful
  • Control flow: The sub-unit is executed as often as specified in the iterations property.
    • strict=false, rollback=true/false: If one of the iterations cannot be executed, the next iteration is executed.
    • strict=true, rollback=false: If one of the iterations cannot be executed, the execution stops.
    • strict=true, rollback=true: If one of the iterations cannot be executed, the execution stops and previous executions are reverted.

Conditional Unit

Henshin Conditional Unit.png
  • Number of sub-units: 2 or 3
  • Available Flags/Properties: none
  • Execution successful if: if unit and then unit are successful or if unit is unsuccessful while then unit is successful or not present.
  • Control flow: If a match for the if unit can be found, the then unit is executed. Otherwise, if present, the else unit is executed.

Back to the top