Moving a part or other usage within a hierarchy

[johnafitch]

What is the simplest mechanism for a user to change the position of a part usage within a hierarchy of parts - without deleting it and losing other useful relationships in the model? Issue #859 seems to indicate a capability to do that by editing nesting relationships, but I don't see in the documentation how to invoke that editor on a part usage.

Solution architectures (or functional models) seldom evolve in a purely top-down fashion without some iteration and refactoring. Most MBSE tools that I used in the past provide an intuitive cut/paste or drag-drop mechanism for restructuring any hierarchy and such moves don't break other relationships. Are there plans for such capabilities in SysON?

[AxelRICHARD]

Hello,

Yes, it is possible to change the hierarchy of parts in SysON diagrams.

Several possibilities:

1. drag & drop the relation ends:

SysON-DnD-Parts.mp4

2. Use the appropriate tools (mentioned in Improve label of "nested" relation creation #859) by connecting a part to another:

SysON-BecomeNestedPart.mp4

For the cut/paste mechanism, there are plans to have d&d in the Explorer view (on the left side of the screen).
At some point (but not planned yet), we also should have the possibility to cut/paste in the Explorer view and in the diagrams.

Regards,

P.S: I'm gonna move this discussion in the Discussions section of this github repository as it is more a Q&A than a real issue.

[johnafitch]

I was able to use the "become nested part" operation to restructure a part hierarchy. And used the ability to move the endpoints of a containment relationship to restructure an action tree. However the latter was kludgy. I wanted to add a higher-level Action to provide some context and then demote the original top-level actions beneath it. I had to create two dummy actions within the top-level node (using the text input mechanism) and "steal" their containment relationships to fix the structure. See end result in the attachment. Is there a better way to add higher-level nodes to the model?

[AxelRICHARD]

I think there is a better way indeed. You can create a new Action (actionB) from the diagram background and then d&d your existing Action (actionA) to the new actionB compartment named action flow.

SysON-GeneralView-DnD-Action.mov

A link tool could also be a good alternative, that's something we could implement.
Regards,