!standard  D.15(24/2)                             10-08-10    AI05-0210-1/02
!class binding interpretation 10-04-24
!status Amendment 2012 10-08-10
!status ARG Approved 10-0-0  10-06-19
!status work item 10-04-24
!status received 10-03-25
!priority Low
!difficulty Easy
!qualifier Clarification
!subject Correct Timing_Events metric
!summary 

The metric for Timing_Events only need consider the case where a single handler
attempts to execute at the time set.

!question

Should the metric D.15 (23/2) explicitly say that only one handler should execute
at the time set? (Yes.)

!recommendation

(See Summary.)

!wording

Modify D.15(24/2):

* An upper bound on the lateness of the execution of a handler. That is, the maximum
  time between {the time specified for the event and }when a handler is actually 
  [executed and the time specified when the event was set]{invoked assuming no other
  handler or task is executing during this interval}.

!discussion



!corrigendum D.15(24/2)

@drepl
An upper bound on the lateness of the execution of a handler. That is, the
maximum time between when a handler is actually executed and the time specified
when the event was set.
@dby
An upper bound on the lateness of the execution of a handler. That is, the maximum
time between the time specified for the event and when a handler is actually
invoked assuming no other handler or task is executing during this interval.


!ACATS Test

Metrics are not testable.

!appendix

****************************************************************