Project

General

Profile

Feature #2166

Extend the deployment-plugin to allow the mapping of messages onto TransmissionUnits/CommunicationResources

Added by Alexander Diewald almost 6 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
Normal
Category:
-
Start date:
11/25/2014
Due date:
% Done:

0%

Estimated time:
30.00 h

Description

Summary

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.


Related issues

Related to Feature #2265: Create a message representation for deployed communicationClosed02/02/2015

History

#1 Updated by Simon Barner almost 6 years ago

  • Target version changed from Phoenix 2.7 Release to AF3 2.7 RC1 (features frozen)

#2 Updated by Alexander Diewald almost 6 years ago

  • Assignee set to Alexander Diewald
  • Target version changed from AF3 2.7 RC1 (features frozen) to AF3 2.8 RC1 (Feature Freeze)

#3 Updated by Alexander Diewald over 5 years ago

  • Related to Feature #2265: Create a message representation for deployed communication added

#4 Updated by Alexander Diewald over 5 years ago

  • Target version changed from AF3 2.8 RC1 (Feature Freeze) to AF3 2.9 RC1 (Features frozen)

#5 Updated by Anonymous almost 5 years ago

  • Status changed from New to Rejected

Also available in: Atom PDF