UPDM2 — ResourceConnector.realizedExchange does not have a programmable direction or other context specific data

ResourceConnector.realizedExchange between same role has no direction.

This causes an issue when there is no natural direction for the exchange, especially when two roles have an identical types. There is also no realization specific measures.

For example. A a structure of a cat box containing two identical resources of the type Kitty with roles a and b. Kitty has an ResourceInteraction to itself defined. In the context of the cat box composite, the only allows the realization of the exchange, but not the direction (a to b or b to a).

The proposal would be a complex type for realized exchanges that includes direction, the exchange, and possible instance specific measures. This solves several issues. Less viable are lists for direction.

This is a complex issue that goes back to the roots of UML if dealt with correctly. A
Workaround was determined if you use roles in the swimlanes of the activity diagram, use of flow ports or provide required ports, all give indication of direction. Which allows this information to be derived.

Therefore it was decided to close this issue with no change.

Proposed Disposition: Closed, no change