Issue 14913: Clarify the semantics of GQAM::BehaviorScenario duration attribute w.r.t. execTime, respTime and hostDemand (marte-rtf)
Source: THALES (Mr. Sebastien Demathieu, sebastien.demathieu(at)thalesgroup.com)
Nature: Clarification
Severity: Critical
Summary: Clarify the semantics of GQAM::BehaviorScenario duration attribute w.r.t. execTime, respTime and hostDemand, and harmonize their use across analysis chapters of the specification. On-going discussion with Dorina and Murray on this topic.
Resolution: Clarified, using a reference to the definitions in Table 15.1. Some of the attributes
like execTime occur in the Table but are not used in the domain model, this is
also clarified
Revised Text: Replace para 5 on p 290 of sec 15.
OLD text:
Steps and BehaviorScenarios have quantitative attributes as shown in Figure
15.3. A Step can be optional (with a probability less than one of being executed),
or repeated (with a repetition count). It can be refined as another
BehaviorScenario (its “behavior” association). The “isAtomic” property specifies
atomicity of execution (default is false).
Replacement text:
Steps and BehaviorScenarios have attributes as shown in Figure 15.3. Most of
these are defined in table 15.1 below, which also defines additional result
variables which could be included in an extended model, but which are not
incorporated in this domain model. In particular, respTime is the end-to-end delay
of a BehaviorScenario, and blockingTime is any pure delay which enters the
Step in addition to delays related to execution of operations. Priority is the priority
of execution of a Step on the host processor, and the isAtomic property specifies
atomicity of execution of the entire Step (the default is false). When combined with issue 15073 which also revises this paragraph, the text
given in red below is also included. The result is:
Steps and BehaviorScenarios have attributes as shown in Figure 15.3. Most of
these are defined in table 15.1 below, which also defines additional result
variables which could be included in an extended model, but which are not
incorporated in this domain model. In particular, respTime is the end-to-end delay
of a BehaviorScenario, and blockingTime is any pure delay which enters the
Step in addition to delays related to execution of operations. A BehaviorScenario
is a collection of Steps, but also a Step can also be the parent of a refinement as
a more detailed BehaviorScenario (its childScenario). Priority is the priority of
execution of a Step on the host processor, and the isAtomic property specifies
atomicity of execution of the entire Step (the default is false).
Actions taken:
December 31, 2009: received issue
January 14, 2011: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 31 Dec 2009 08:09:46 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:          SĂ©stien Demathieu
Company:       Thales
mailFrom:      sebastien.demathieu@thalesgroup.com
Notification:  Yes
Specification: MARTE
Section:       GQAM
FormalNumber:  09-11-02
Version:       1.0
RevisionDate:  11/2009
Page:          289
Title:         Clarify the semantics of GQAM::BehaviorScenario duration attribute w.r.t. execTime, respTime and hostDemand, and harmonize their use across analysis chapters of the specification
Nature:        Clarification
Severity:      Critical
test:          3qw8
B1:            Report Issue


Description:

Clarify the semantics of GQAM::BehaviorScenario duration attribute w.r.t. execTime, respTime and hostDemand, and harmonize their use across analysis chapters of the specification. On-going discussion with Dorina and Murray on this topic.