Extend the deployment-plugin to allow the mapping of messages onto TransmissionUnits/CommunicationResources
Currently, the deployment plugin supports mapping of Components onto ExecutionUnits and Ports onto Transceivers. For more complex communications (like in hierarchical platforms), it is required to deploy a whole message (or better: its sub-transmissions) onto the participating CommunicationResources.
Detailed Description/Initial Thoughts¶
For the multi-hop communication introduced above, a route must serve as an input, which does not have a single port as an equivalent, like in single-bus systems. Thus, it might be required to define the notion of a message that needs to be routed (or that can reference an automatic, pre-calculated routing). Depending on the possibilities that shall be given to the user, there might be large conceptual and UI overhaul required.