Skip to main content
Jump to: navigation, search

Henshin/Transformation Meta-Model

< Henshin
Revision as of 12:08, 2 June 2014 by (Talk | contribs) (Advanced concepts: Rule refinement)

The Henshin transformation meta-model defines the concepts used for the specification of model transformations in Henshin.

Model transformations are defined in modules that comprise a set of units, being either transformation rules - atomic units - or composite units that allow to define a control flow.

Basic building blocks: Rules

Henshin Transformation Modules.png

Rules are the basic building blocks of model transformations in Henshin. A rule comprises two graphs, a left-hand side (LHS) and a right-hand side (RHS) graph. LHS and RHS specify model patterns on abstract syntax level. Nodes correspond to model elements, edges correspond to references owned by and typed over model elements. The LHS describes a pattern to be matched. The RHS specifies a change on the input model. Nodes and edges occurring in the LHS or RHS only are deleted or created, respectively. Node mappings between LHS and RHS declare identity, that is, nodes and edges being preserved. In the graphical editor, nodes are shown with a «create», «delete», or «forbid» tag determined by their containment in LHS and/or RHS graphs. Nodes possess attributes. Attribute conditions can be defined whose expressions are evaluated by a JavaScript engine at runtime.

Dangling condition: A common beginner-level problem is that rules are deemed unexecutable by the Henshin interpreter despite looking correct at the surface. This behavior is often connected to the dangling condition: A rule execution may not leave behind dangling edges, being edges with a missing source or target. It is possible to turn the gluing condition check off using the checkDangling Boolean flag.

Injective matching: The injectiveMatching flag specifies whether the match-finder is allowed to assign two or more LHS nodes to the same model element. Per default, matching is set injective (e.g., it is not).

Advanced concepts: Rule refinement

Henshin Application Conditions.png

Application conditions are graph patterns which restrict the LHS of a given rule during application. They may require the presence of additional elements or relationships not included in the LHS. In this case, they are referred to as positive application conditions (PACs). Furthermore, they may forbid the presence of elements or relationships in the LHS. In this case, they are referred to as negative application conditions (NACs). Consequently, the graphical editor displays PAC elements with a «forbid» and NAC elements with a «forbid» tag. Application conditions can be arbitarily nested using the propositional operators Or, And, Xor, and Not. Whether an application condition graph represents a NAC or a PAC is determined by its containment in a Not condition.

Rule-nesting is a powerful concept providing a for-each operator for rules. In nested rules, the outer rule is referred to as kernel rule and an inner rule as multi rule. During execution of a nested rule, the kernel rule is matched and executed once and used as a starting point to apply the multi rule as often as possible. Multi mappings allow to specify identity between kernel and multi rule nodes.

Control flow: Units

Henshin Transformation Units.png

In Henshin, control flow is specified using units. Units have a fixed number of sub-units, allowing for arbitrary nesting. The following unit types are available:

Sequential units have an arbitrary number of sub-units that are executed in the given order. The Boolean flag strict determines the behavior if one of the sub-units cannot be executed: In strict mode, the execution stops, otherwise, the next sub-unit is executed. The Boolean flag rollback determines whether in the case of a stopped execution previous executions are reverted.

Priority Units have an arbitrary number of sub-units that are checked in the given order for executability. One sub-unit - the first one found to be executable - is executed.

Independent Units have an arbitrary number of sub-units that are checked in nondeterministic order for executability. One sub-unit - the first one found to be executable - is executed.

Loop Units have one sub-unit. The sub-unit is executed as often as it is executable.

Iterated Units have one sub-unit. The sub-unit is executed as often as specified in the iterations property.

ConditionalUnits have either two or three sub-units: if, then, (and else). If a match for the if unit can be found, the then unit is executed. Otherwise, if present, the else unit is executed. Note that any changes specified in the if unit are ignored; it is used for matching only.

Execution-time variability: Parametrization

Henshin Parameters.png

Parameters allow to shape the behavior of units and rules with variable information that is typically not present before execution time. Parameters are defined as part of the rule and can then be used in elements of the rule, e.g., as attributes and in attribute conditions. Parameters can be set from the environment using the API or the graphical interpreter wizard. Parameters values set from the environment are used during matching. In turn, parameters that were not set from the environment are set by the matchfinder to the values found in the respective objects. This can be used to propagate values between LHS and RHS elements.

Parameter mappings: In order to pass parameter values from outer to inner units, it is required to define parameter mappings. A parameter mapping assigns a source parameter to a target parameter.

Back to the top