Alignment of functional chain

[ravidixit]

Hello,
For my project, as the complexity of the Logical Architecture increased the diagram became clumsy. Is there any better way of arranging the functions/functional exchanges so that there is no overlapping /crossing? Any auto or manual methods feature suggestion will be of great help.

Thanks
Ravindra Dixit

[StephaneLacrampe]

Hi Ravindra,

There are quite a few things you can look at in the documentation about diagram management and layout strategies:

• https://github.com/eclipse/capella/blob/master/doc/plugins/org.polarsys.capella.ui.doc/html/05.%20Diagram%20Management/5.2.%20Advanced%20Management%20of%20Diagrams.mediawiki
• https://github.com/eclipse/capella/blob/master/doc/plugins/org.polarsys.capella.ui.doc/html/05.%20Diagram%20Management/5.1.%20Diagram%20concepts.mediawiki#Layout_Management
• https://github.com/eclipse/capella/blob/master/doc/plugins/org.polarsys.capella.tipsandtricks.doc/html/Tips%20and%20tricks/8_Other%20layout%20facilities/8_Other%20layout%20facilities.mediawiki
• https://github.com/eclipse/capella/blob/master/doc/plugins/org.polarsys.capella.tipsandtricks.doc/html/Tips%20and%20tricks/5_Layout%20management/5_Layout%20management.mediawiki
  (here is the entry for the online online manual: https://github.com/eclipse/capella/wiki/User-manual)

Let me make an additional comment: At some point, if you are modeling a big complex system, you will have so many components and functions at the logical architecture level or physical architecture level, that your diagram will eventually become too complex. So it is a good practice to:

• make a master diagram you use as a footprint displaying for instance only components
• create more focused architecture daigrams where you show only a sub part of all your componends and their functions
• copy and paste the layout of your footprint diagram so that all focused diagram have a consistent layout (the Capella IFE exemple has some good examples of this)
• ans also: you may have diagrams you use to work on your model, with a lot of elements, where you do not spend to much time on layouting, and others you use to communicate, where you pay attention to layout and readability

I hope this helps.

All the best,
Stephane

[ravidixit]

Thank you Stephane for your valuable time and pointers. It helps.