Have create separate meta-model for BehaviourTree in Capella
Now it’s possible to add BehaviourTrees in function, capability and component elements for all Capella model levels (OA, SA, LA, PA)
Elements can be created via model browser using standard Add Capella Element menu
I need to make a decision now about linking leaf-nodes to functions.
There is an architecture trade betwee
- 1 to 1 mapping (one leaf node of BTree is linked to one atomic function)
- 1 to N mapping (one leaf node of BTree is linked to several atomic functions)
Currently I’ve selected 1 to 1 mapping.
1 to N mapping can be compared to statechart possibility to add several functions for entry\do\exit actions
May be In BTree this approach should be also used.
Abother decision about link implementation
- using an attribute in leaf-function
- using separate link elements that cab be added to leaf-functions
In the second case it will be possible to show linked functions in Model Browser.