Object Run State in SysML 1.2 Parts

[philchudley]

Hi all

I am trying to model Trade-offs in SysML 1.2, where a structural model can be instantiated as parts and then the run state can be set for each part and appropriate values entered corresponding to attributes in the block.

This is pretty much equivalent to instantiating Classes as Objects in UML, but that is where the comparison ends!

I am using the latest build of EA version 9.2

First, if valueTypes are used as values of the blocks, then the object state cannot be set, since the variable drop down list is blank. Attributes MUST be used as in UML.

Secondly, when a number of blocks are re-used as properties (equivalent to reusing UML classes as objects), and selecting Copy Connectors ... the connectors DO NOT appear as they do in UML!

Thirdly, although the runstate of a part can be set, the run state is NOT visible on the object diagram, as it does in UML!

Workround ... for the parts, remove each stereotype and the runstate appears.

Workaround ... for the connectors, copy all the Blocks, remove the stereotypes and create the object diagram (also displays the run state)

Both workarounds are clumsy.

Any other SysML modellers out there, found the same, or know of a better workround.

Is the behaviour I have described expected ... a feature ... or a another bug in the SysML implementation?

Cheers

Phil

[qwerty]

I guess it's due to the fact that the stereotypes have a shape script. And each of those overwrites the display of the element. And along with that the run state.

You should report that as bug to Sparx since they have to find ways to  show the run state in the shape script.

q.