Issue 14897: SecondaryScheduler should be an association of the Scheduler instead of a specialized class (marte-rtf) Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com) Nature: Revision Severity: Minor Summary: 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 Resolution: 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. Revised Text: Actions taken: December 31, 2009: received issue January 14, 2011: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 31 Dec 2009 07:36:21 -0500 To: Subject: Issue/Bug Report ******************************************************************************* Name: Séstien Demathieu Company: Thales mailFrom: sebastien.demathieu@thalesgroup.com Notification: Yes Specification: MARTE Section: GRM FormalNumber: 09-11-02 Version: 1.0 RevisionDate: 11/2009 Page: 97 Title: SecondaryScheduler should be an association of the Scheduler instead of a specialized class Nature: Revision Severity: Minor test: 3qw8 B1: Report Issue Description: 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.