MARTE_ — Figure 16.6: multiplicity

Figure 16.6: multiplicity for the host of a SchedulableResource shoudnt it be 1 - In the example (Figure 16.13), the SchedulableResources associated to SaCommHost, Shouldnt they be CommunicationChannels? - The constraints in 10.3.2.16 (SecondaryScheduler) should be also in its domin concept defined in annex F. - It is not clear the relationship between the clockOverhead of a SaExecutionHost and the TimingResources associated

Figure 10.11, “The Scheduling Package” expresses that a
SchedulableResource has at most one host. While a resource could be
scheduled by two or hosts, management of such distributed scheduling is beyond
the original intent. Figure 16.6 should be corrected to show the host role to be of
multiplicity 0..1.

• We agree that the schedulable entities allocated to the SaCommHost CAN Bus
  should be CommunicationChannels.
• The SecondaryScheduler is described in F.4.33. The mentioned constraint
  should be added.
• clockOverhead is only cited as an Attribute of an ExecutionHost and no
  explanation is provided. The purpose of the Attribute should be described.