-
Key: MARTE13-14
-
Legacy Issue Number: 18657
-
Status: closed
-
Source: Simula Research Laboratory ( Dr. Bran Selic)
-
Summary:
In the current UML metamodel, there is no link from the metaclass Observation to a ValueSpecificaiton that can be used to specify the time value of the Observation. As a result, it is not possible to directly assign time values to TimedInstantObservation or TimedDurationObservation.
This means that it is not possible to refer to the time values of such observations in a time expression.
One easy solution is to create an association from the TimedObservation stereotype to the UML ValueSpecification metaclass (role name "value"). This could then be used to store the time value associated with either kind of time observation.
-
Reported: MARTE 1.0 — Fri, 12 Apr 2013 04:00 GMT
-
Disposition: Resolved — MARTE 1.3
-
Disposition Summary:
Add associations to UML ValueSpecification from TimedInstantObservation and TimedDurationObservation stereotypes
Modify the UML representation by:
- adding value role of type ValueSpecification to TimedInstantObservation and TimedDurationObservation stereotype
- no need to modify the domain model because the issue of the missing value placeholder comes from UML
-
Updated: Mon, 2 Oct 2023 12:56 GMT
-
Attachments:
- attached-fig9-29.PNG 35 kB ()
MARTE13 — MARTE issue: Observation does not allow specification of time value
- Key: MARTE13-14
- OMG Task Force: MARTE 1.3 RTF