Using behaviour three notation for behaviour description in Capella in comparison with statechart notation

Recently have updated BehaviourTreeExtension to Capella version 5.2.0

source code is here

current update site is on the link

extension adds possibility to create Behaviour Trees for components and (atomic) functions.
in BTree for a component it’s possible to “call” functions allocated to component
in Btree for a functions it’s possible to to “call” functions with output functional exchanges from current function

We use this version currently to define control flows for functions and components in some our projects.
for components it’s an alternative to statecharts

Short demo of current version