The Operational Exchanges and Resource Exchanges can be inherited, aggregated, or composed. You can redefine the inherited flows.
You can see the inherited, aggregated, and composed exchanges in:
Case Study
Let's say, we have Operational Performers Search Node and Place Of Safety related with the Operational Exchange Warning Order. The Operational Performer Aircraft specifies Operational Performer Search Node. Then we draw an association between Aircraft and Place Of Safety. In this case, the drawn association inherits the Operational Exchange information that can be realized or not and also can be redefined.
Let's realize the Operational Exchange. We can do this in two ways:
To hide inherited exchanges in dialogs
|
|
All the inherited exchanges can be also seen in the role-based tables. The inherited exchange rows are displayed in gray.
To see the inherited exchanges
When we have the inherited Operational Exchange, we can redefine it. This means, that the inherited Operational Exchange will be copied together with the information such as Actual Measurements, Conveyed Items, Documentation. The new Operational Exchange will be created in the model.
To redefine the Operational Exchange
All the information that comes from the inherited exchange when redefining it can be modified in the model. |