MARTE11 — SecondaryScheduler should be an association of the Scheduler instead of a specialized class

For the sake of simplicity, SecondaryScheduler should be an association of the Scheduler instead of a specialized class. Making this concept relative would provide means to support more than two-level schedulers. Requires changes in the meta-model and the profile

This simplification is not possible since the mechanisms to share the capacity
that will be rendered by the primary scheduler to the secondary in order to be
brokered by the secondary needs to be expressed, and this is done by the
utilization of the intermediate schedulable resource.
Simpler models may be made at user model level, so that the association
between them can be stereotyped as Schedulable resource, but that is not
feasible at the profile or domain view level.
Resolution:
Closed the issue with no change to the specification.