py-capellambse and state machines

[khammoutene]

I am modelling states machines and I am trying to access to the “effects” using py-capellambse.

I have modelled both an effect in a transition and in a state.

Capella is restricting me to Service elements to describe effects that’s why you see “Service 3” in the diagram. I was expecting to be able refer to functions for an effect but this is not my question to you
(I have created a topic discussion in: [https://forum.mbse-capella.org/t/modelling-effects-in-state-transitions-in-a-state-machine/5833]

This is a basic model:

My question to you is that I cannot see “Service 3”, i.e. effects, in both the state information and transition information that I am accessing via py-capellambse.

<State 'Draft' (dd843949-ae9b-4161-bd2d-b53c239feb07)>
.constraints = []
.description = None
.diagrams = []
.functions = []
.name = 'Draft'
.parent = <Region 'Default Region' (c417fb92-670a-4f03-b782-cb7504368856)>
.progress_status = 'NOT_SET'
.realized_states = [0] <State 'Draft' (c127914c-0b8b-42ee-b3b6-510482a2df74)>
.realizing_states = []
.regions = [0] <Region 'region' (30ecb727-0033-4582-8f36-4d639b79901c)>
.requirements = []
.summary = None
.traces = []
.uuid = 'dd843949-ae9b-4161-bd2d-b53c239feb07'
.xtype = 'org.polarsys.capella.core.data.capellacommon:State'

<StateTransition '' (571bd05e-8303-4fc2-89c9-4dac757a72e1)>
.constraints = []
.description = None
.destination = <State 'Draft' (dd843949-ae9b-4161-bd2d-b53c239feb07)>
.diagrams = []
.guard = None
.name = ''
.parent = <Region 'Default Region' (c417fb92-670a-4f03-b782-cb7504368856)>
.progress_status = 'NOT_SET'
.requirements = []
.source = <JoinPseudoState '' (5f210683-853e-4c76-a26c-a04c35ad4bbb)>
.summary = None
.traces = []
.triggers = [0] <Model element (org.polarsys.capella.core.data.capellacommon:ChangeEvent) 'Back to draft' (d7bab880-0620-4d88-b587-2306ddd0009e)>
.uuid = '571bd05e-8303-4fc2-89c9-4dac757a72e1'
.xtype = 'org.polarsys.capella.core.data.capellacommon:StateTransition'

Do you have any idea why?

Thank you,

[Wuestengecko]

Looks like we simply don't have what you're looking for yet. I've made a PR to add the effects attribute to StateTransition objects in #174.

[vik378]

I dont think it is correct to call this "effects":

These are activities that get executed on state entry / exit or while in state, so it should rather be

• entry
• do_activity
• exit

[vik378]

For StateTransition, .effects seem to be independent from the target state entry entry - effects is basically a thing on its own

[khammoutene]

Thank you @ewuerger

I will come back in few months.

[vik378]

well, I don't think it is months though.. our approach to coverage so far was (and will remain) reactive - when we or a external contributor find a missing thing we or external contributor propose a fix for it. We made a few attempts on 1:1 metamodel to code but we weren't convinced by the outcome. It is nice that you found missing bits on state machines, @khammoutene - this also goes along with one of the things from the methods backlog (stm to text) - and the fix for those 3 missing properties should be pretty trivial - maybe I draft it this evening and maybe it gets through the review sometimes this week or so.

[vik378]

oh, and I see that @ewuerger already did with #181 🥳

[ewuerger]

well, I don't think it is months though.. [...]

I was referring to the introductory page of our concrete Accessors when I wrote in the next months. I know atleast that it won't happen this november.

[khammoutene]

Thank you for your reactivity.

Do you have experience in developing Python code combining your approach with Py4C as I see value in both?