Issue 5309: Figure 27 (uml-scheduling-ftf)
Source: The MathWorks (Mr. Alan Moore, alan.moore(at)mathworks.co.uk)
Nature: Uncategorized Issue
Severity: 
Summary: What is the relation of Figure 27 with UML 1.3 DataType package and the metaclass TimeExpression

Resolution: see below
Revised Text: -- insert the following text as the last paragraph in section 4.2.1 and just before section 4.2.1.1:

UML defines a data type called TimeExpression that denotes "a statement which will define the time of occurrence of an event". The intent of this is to specify values of time that are to be used at run time. We refer to such values as run-time values. For example, an instance of TimeExpression would be used to define the value of some periodic interval timer. However, when the corresponding program is executing, due to dynamic loads and other complex run-time effects, the actual measured values of the interval may differ somewhat from the one specified.

In analyses, it is often necessary to factor in these variations by modeling the value of this interval by, say, a probability distribution. Such a probabilistic value specification is generally not useful or even meaningful at run time. We will call such values analysis values. Note that, in contrast to run-time values, analysis values are specific to the type of analysis performed. Thus, there could be many different ways of modeling the same run-time value

For this reason, even though there may be a functional relationship between a run-time value and its corresponding analysis values, the method for specifying analysis values is not based on TimeExpression. Keeping these two sets of values correlated is a problem that is outside the scope of this profile.

Based on the same reasoning, the modeling of timed events in this profile is distinct from the standard UML concept of TimeEvent.

Actions taken:
May 22, 2002: received issue
September 24, 2004: closed issue
Discussion: 
I thought we had fixed this one in the FTF, but after reviewing the document I realize that I had not (again, I believe that I read more into this issue than what was reported - this must be the reason why I did not fix it). This should be easily fixed with a small comment in section 5.2.1.2.
End of Annotations:=====
This is issue # 5309

Figure 27

What is the relation of Figure 27 with UML 1.3 DataType package and
the metaclass TimeExpression