-
Key: MARTE11-51
-
Legacy Issue Number: 14221
-
Status: closed
-
Source: Commissariat a l Energie Atomique-CEA ( Dr. Sebastien Gerard)
-
Summary:
The description of the semantics of TimedObserver in section F10.18 has to be aligned with its description denoted in the diagram shown in figure 15.4. TimedObserver can refer to several start and end events.
-
Reported: MARTE 1.0 — Wed, 26 Aug 2009 04:00 GMT
-
Disposition: Resolved — MARTE 1.1
-
Disposition Summary:
{Fig 15.4 shows multiplicity * for both start and end events. Sec F10.18 shows
multiplicity 0..1 for both... this should be changed to *. Since there may be
several pairs of events, the associations must be ordered to express the
correspondence. Since the is also an attribute laxity for each pair, it must also be
multiple and ordered.
Also there is confusion in the naming of the associations: startObs and endObs
in the text in F10.18 and of Ch 15 for domain and UML, and startEvent and
endEvent in the formal definition of F10.18 and in Fig. 15.4, and in the profile
definition (sec 15.3.2.14). One or the other should be used consistently. Since
startEvent/endEvent is rather generic, and indeed is also used in the Core
domain model in another sense, it is preferred to standardize on startObs and
endObs. -
Updated: Fri, 6 Mar 2015 23:15 GMT