Issue 12371: MARTE-GQAM) Kinds of delay in a Step (marte-ftf) Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca) Nature: Uncategorized Issue Severity: Summary: Generated, based on extensive discussion, to deal with the issue raised in 11882, whose resolution is only for SAM. There are two kinds of delay in a step ... self-initiated delays like sleeping or thinking or some latency included in the step, ... blocked delay waiting for an event initiated by some other thread of behaviour The latter is represented by the domain concept Step.blockingTime, which is the profile property gaStep.blockT. The former is not represented. It should be added. Proposed resolution: 1. In GQAM, add the domain property Step.selfDelayTime:NFP_Duration and the profile property gaStep.selfDelayT:NFP_Duration. Add text to the domain model to explain selfDelayTime Add the definition of selfDelayT to the UML representation. 2. In PAM examples, many Steps have internal delay represented as a value of blockT, all of these should be changed to selfDelayT. Resolution: 1. In GQAM, add the domain property Step.selfDelay:NFP_Duration and the profile property gaStep.selfDelay:NFP_Duration. Add text to the domain model to explain selfDelayTime Add the definition of selfDelay to the UML representation. 2. In PAM examples, many Steps have internal delay represented as a value of blockT, all of these should be changed to selfDelay. Revised Text: (1) modify domain text: modify last row and add a row to Table 15.1 which defines common NFP attributes for analysis: old last row: col 1: blockingTime: NFP_Duration[*] col 2: blocking time (N/A) col 3: a pure delay which is part of the behavior of the Step or Scenario col 4: N/A modified row: col 1: blockingTime: NFP_Duration[*] col 2: blocking time (N/A) col 3: a pure delay waiting for passive resources to be available or an event controlled from elsewhere (value is an output variable) col 4: N/A additional row: col1: selfDelay: NFP_Duration[*] col2: delay col3: a pure delay controlled or requested by the Step. (value is an input variable) col4: N/A (2) Fig 15.3, add attribute to GaStep class in domain model: selfDelay:NFP_Duration[*] (3) Fig 15.7, add attributes to GaStep class in profile: selfDelay:NFP_Duration[*] (4) Sec. 15.3.2.13, change the UML definitions: old text: § blockT: NFP_Duration [*]: a delay inserted in the execution of the Step. new text: § blockT: NFP_Duration [*] a delay inserted in the execution of the Step, waiting for an event controlled elsewhere (by another step or scenario), or for a condition such as the availability of passive protected resources nedded by the step but in use by preempted (i.e. lower priority schedulableResources) concurrent steps. § selfDelay: NFP_Duration [*] a delay inserted in a Step, whose duration is controlled or requested by the Step (e.g. a sleep time). {Precise editing instructions for applying resolution, including exact text, models, diagrams, references to be included or deleted. NOTE: IDL should be shown in Courier font} Actions taken: April 1, 2008: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== te: Fri, 4 Apr 2008 15:50:50 -0400 (EDT) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: issues@omg.org Subject: NEW ISSUE: (MARTE-GQAM) Kinds of delay in a Step (fwd) I sent this before but it hasnt surfaced that I saw... Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html) ---------- Forwarded message ---------- Date: Tue, 1 Apr 2008 09:04:59 -0400 (EDT) From: Murray Woodside To: issues@omg.org Subject: (MARTE-GQAM) Kinds of delay in a Step Generated, based on extensive discussion, to deal with the issue raised in 11882, whose resolution is only for SAM. There are two kinds of delay in a step ... self-initiated delays like sleeping or thinking or some latency included in the step, ... blocked delay waiting for an event initiated by some other thread of behaviour The latter is represented by the domain concept Step.blockingTime, which is the profile property gaStep.blockT. The former is not represented. It should be added. Proposed resolution: 1. In GQAM, add the domain property Step.selfDelayTime:NFP_Duration and the profile property gaStep.selfDelayT:NFP_Duration. Add text to the domain model to explain selfDelayTime Add the definition of selfDelayT to the UML representation. 2. In PAM examples, many Steps have internal delay represented as a value of blockT, all of these should be changed to selfDelayT. Murray Woodside Distinguished Research Professor Dept of Systems and Computer Engineering, Carleton University, 1125 Colonel By Drive, Ottawa K1S 5B6, Canada. (613)-520-5721.....fax (613)-520-5727....cmw@sce.carleton.ca (http://www.sce.carleton.ca/faculty/woodside.html)