Legacy Issue Number: 12417
Source: THALES ( Sebastien Demathieu)
GQAM Observers: inconsistency between domain view and UML representation Details: In the domain view (Figure 15.4), the Timing/TimedObserver has two properties startObs and endObs, typed by MARTE::Time::TimedInstantObservation. In the UML profile diagram (Figure 15.8), the related GaTiming/TimedObserver has two properties startObs and endObs, typed by UML::TimeObservation. In the UML profile description (p.281), the same GaTiming/TimedObserver has two properties startObs and endObs, typed by MARTE::Time::TimedInstantObservation. We need to choose whether a timed observer relates to a MARTE TimedInstantObservation or UML TimeObservation, and then to align the domain view, profile definition and profile description accordingly.
Reported: MARTE 1.0b1 — Thu, 24 Apr 2008 04:00 GMT
Disposition: Resolved — MARTE 1.0b2
In the conceptual domain model, we rely in MARTE "concepts", independently of
whatever UML construct. For that reason we use the concept coming from the Time
However, in the profile view, it is permissible to use the UML corresponding metaclass,
because there is no reason to constraint such TimedObservers to Observations
stereotyped with the MARTE Time concepts. (The time concepts add the notion of
clocked Observation (attribute "clock"), which are not essential here). We agreed with
Charles Andre that such a stereotype should not be mandatory when
defining a TimedObserver.
Updated: Fri, 6 Mar 2015 20:58 GMT