Domain Diagram Type

• Prepare a new actifsource Project as seen in the Actifsource Tutorial Statemachine
• Create a generic Domain Model as shown above
• State.transition 🡪 Decorating Relation with Decorator State.-state.event
• Transition.targetState 🡪 Use Relation with RangeRestriction Transistion.-transition.-state.state

• Create a user defined diagram type to display and edit domain specific diagrams

Create a Diagram Type

• Create a new DiagramType named Statemachine in the Package generic

• The Root Class defines the Resource which contains the elements that shall be managed on your domain diagram

• Select Statemachine as Root Class

• The Allowed Class defines all the Resources which shall be managed on your domain diagram

• Select State as Allowed Class since we want to design a state machine

• Allowed Classes might be created using the domain diagram editor via a Palette Tool

  • HidePaletteEntry: No Palette Entry to create this Allowed Class
  • ShowPaletteEntry: Palette Entry named as the Allowed Class
  • ShowRenamedPaletteEntry: Palette Entry named as defined

• Select the PaletteEntry ShowPaletteEntry or ShowRenamedPaletteEntry

• Allowed Relations are relations that shall be displayed on the domain diagram

  • AllowedDependencyRelation: Dotted Line that shows dependencies between components
  • AllowedDirectRelation: Direct relation between resources A and B
  • AllowedIndirectRelation: Indirect relation between resources A and B via X

• We like to see a transition from state to state just as a simple arrow

• Define the Selector State.transition.targetState for the Indirect Relation

• Define openEditor as false if you do not want to open the Resource Editor automatically after creating the transition via domain diagram editor.

• Create a domain diagram based on the diagram type to edit the underlying root resource

• Create a new Statemachine named Statemachine1 in the Package specific

• We could now define Event, State and Transition using the Resource Editor
• Let’s now try the Domain Diagram Editor

• Create a new Domain Diagram named Statemachine1 for the Statemachine Statemachine1 in the Package specific
• Use the context menu directly on the Statemachine Statemachine1

• The domain diagram shall be named Statemachine1
• DiagramType is detected automatically based on the Root Resource
• Single Root is filled in automatically based on the context of new Domain Diagram

• Create new States named Open Close Opening and Closing using the State Tool from the Palette

• Start adding Transitions using the Relation Tool from the Palette

• Therefore you are asked for an Event when creating a new Transition
• Create a new Event called Command_Close using Content Assist (or choose an existing Event

• The Event Command_Close has been created
• The Transition based on the Event Command_Close with targetState Closing has been created

• Add some more Transitions based on the new Events Command_Open Sensor_Closed Sensor_Opened

• Add two more Transitions based on the existing Events Command_Close and Command_Open
• Use Context Assist to choose the existing Events

• Define a highlight path from node to node over any edge

• Let’s see where transitions are leading to from source to target state
• Define a HighlightPath for the Allowed Class State as shown in the example above

• Hoover your cursor on any State to activate the HighlightPath from State via Transition to TargetState

• Define a tooltip for elements on the domain diagram

• Create a new FunctionSpace named Tooltip in the Package generic

• Create a new ResourceInfo with typeRef State
• Create a new TemplateFunction named tooltip

• Open the Template Editor by double clicking Tooltip.State.tooltip in the Project Explorer

• Print the State.name
• For every Transition in State: Print Transition.event.name
• For every Transition in State: Print Transition.targetState.name

• Use the TemplateFunction tooltip@Tooltip by using a SelectorTooltip in the Diagram Type

• Hoover your cursor on any State to activate the Tooltip