Issue 12225: TimingResource of GRM (marte-ftf) Source: INRIA (Dr. Frederic Mallet, Frederic.Mallet(at)inria.fr) Nature: Revision Severity: Critical Summary: My concern is about the TimingResource of GRM. In the domain model (10.2.2, p.89-90 and figure 10.7), TimingResource both refers to a Clock (since it is a Resource) and specializes ChronometricClock. The specialization is not suitable since a TimingResource is not a clock (with the meaning given in the Time profile) but merely refers to a Clock. To make a TimingResource specific to chronometric clocks, it is largely sufficient to refine the association to a Clock by an association to a ChronometricClock. In the UML representation (Figure 10.15) and in 10.3.2.20 I would simply remove the specialization to ClockType. The reference to a Chronometric Clock (idealClock in this precise case) is already implicit by the use of the NFP_Duration type. If you really want to insist on the use of chronometric clock only, a comment in the text should do it. Resolution: We propose to remove the specialization from TimingResource to ChronometricClock in the domain view. In the UML representation, we remove the specialization from ClockType. This latter specialization is very problematic since Resource extends several metaclasses (Property, InstanceSpecification, Classifier, Lifeline, Connectableelement) and ClockType only extend Class. The specializations are not required since a TimingResource being a resource can already access to information of Clocks (including if required, ChronometricClocks). Revised Text: see ptc/2009-05-12 pages 171 - 172 Actions taken: February 15, 2008: received issue October 16, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 15 Feb 2008 07:45:53 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Dr. Frederic Mallet Company: INRIA mailFrom: Frederic.Mallet@sophia.inria.fr Notification: No Specification: MARTE Section: 10 FormalNumber: ptc/07-08-04 Version: beta 1 RevisionDate: 08/04/07 Page: 89-90;97;110 Nature: Revision Severity: Critical HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12 Description My concern is about the TimingResource of GRM. In the domain model (10.2.2, p.89-90 and figure 10.7), TimingResource both refers to a Clock (since it is a Resource) and specializes ChronometricClock. The specialization is not suitable since a TimingResource is not a clock (with the meaning given in the Time profile) but merely refers to a Clock. To make a TimingResource specific to chronometric clocks, it is largely sufficient to refine the association to a Clock by an association to a ChronometricClock. In the UML representation (Figure 10.15) and in 10.3.2.20 I would simply remove the specialization to ClockType. The reference to a Chronometric Clock (idealClock in this precise case) is already implicit by the use of the NFP_Duration type. If you really want to insist on the use of chronometric clock only, a comment in the text should do it.