Missing Graphical Elements in Instantiated Parts from Part Def

[MCourtec]

I have a question about the instantiation of an object of type "part" from an object of type "part def" (with a FeatureTyping link).

In my understanding, this process is comparable to an instance/class relationship in object-oriented programming. The instance should inherit all the characteristics of its original class.

However, in SysON, this inheritance appears to be only partial.
In the given example, "part2" is an instance of "PartDefinition1". It has inherited "portAlpha", "portBeta", and "action1", except that they have been renamed "^portAlpha", "^portBeta", and "^action1".

However, they do not appear graphically on the instantiated part. For example, to view and use/connect "portAlpha", you need to manually create a port and rename it "portAlpha" for it to be usable.

If my understanding is correct, I'm wondering what the purpose of defining part defs is if each element has to be manually redefined when needed?

Is this expected behavior according to the SysON specifications, or is it an error?

[AxelRICHARD]

Hello,

My answers below:

In the given example, "part2" is an instance of "PartDefinition1". It has inherited "portAlpha", "portBeta", and "action1", except that they have been renamed "^portAlpha", "^portBeta", and "^action1".

They have not been renamed, we choose to display inherited members in italic and prefixed by a ^. (https://doc.mbse-syson.org/syson/v2025.4.0/user-manual/release-notes/release-notes.html, search for "New "Show/Hide Inherited Members in Diagrams" diagram panel entry")

However, they do not appear graphically on the instantiated part. For example, to view and use/connect "portAlpha", you need to manually create a port and rename it "portAlpha" for it to be usable.

We choose to not display inherited members as ports.
Most of the time, you want to subset/redefine inherited members (see how to subset/redefine an Element in the SysMLv2 specification https://github.com/Systems-Modeling/SysML-v2-Release/blob/master/doc/2a-OMG_Systems_Modeling_Language.pdf).
So in your example, if you need to use portAlpha in part2, subset it with a new Port (for example myPortAlpha :> portAlpha, see https://doc.mbse-syson.org/syson/v2025.4.0/user-manual/hands-on/tutorials/batmobile.html#_creating_subsetting) or redefine it (for example myPortAlpha :>> portAlpha, see https://doc.mbse-syson.org/syson/v2025.4.0/user-manual/hands-on/tutorials/batmobile.html#_creating_redefinition).

Hope it will help you!

Regards,