Functional exchange type merging

Hi,

I would like to know if it’s possible de merge same type of functional exchange in order to decrease the number of exchange and make my diagram easier to read but without losing all information that must be exchanged.

Ex : my system must analyse some KPI and develop suggestions to be communicated to an operator. operator can then accept or refuse with justification. I would like to create one functional exchange “Suggestion feedback” that can contain either the acceptance or refusal with explanation.

I tried to look in the “applied property value” of the functional exchange but not sure how to use it…

Thank you for your help!

Kind regards,

Vincent.

Hi Vincent,

Are the functional exchange categories (or even just the graphical simplification) potential solutions in your case?
(see Capella: Manage model complexity for illustration)

Copyright © Eclipse Capella, the Eclipse Capella logo, Eclipse and the Eclipse logo are Trademarks of The Eclipse Foundation.