Issue 11774: GQAM: Domain Model & Profile (01) (marte-ftf) Source: Fundacion Tecnalia Research and Innovation (Mr. Huascar Espinoza Ph.D., Huascar.Espinoza(at)tecnalia.com) Nature: Enhancement Severity: Significant Summary: [GQAM: Domain Model & Profile] The PrecedenceRelation concept (fig 15.3) could be used to specify delays due to e.g., queues. However, PrecedenceRelation only exists in the Domain Model. Its implementation is intended to be supported by existing UML concepts (e.g., forks, joints, etc.) I’d suggest to define the corresponding stereotype (<<PrecedenceRelation>>) in order to allow for modelling delays or other precedence patterns like event divisors: a number of event occurrences triggers an execution. Resolution: This enhancement is not necessary, since everything it would provide can already be done using scenario Steps, and done better. However the method for showing an event divisor using steps should be added to the text. Since a precedence relation always leads to one or more steps, properties such as queueing etc can be attached to the step. The step is a better place for these properties because there may be multiple branches in a precedence relation (a branch or fork), each with its own properties. For example, a fork precedence would have a different waiting on each branch of the fork, which would be complex to describe or specify within the fork, but very easy on the following steps. An event divisor or multiplier can be provided using the CommStep stereotype. We assume that the event is a call invoking a Step. The call can be stereotyped as a CommStep, which has a repetition attribute. If this is set to N, it means the call is repeated N times, giving event multiplication. If it is set to 1/N, it means that every Nth execution of the sender gives a call... an event divisor. If the repetition attribute is specified as a deterministic NFP, it should be defined to be interpreted as 1/N for an integer N, determined by rounding to an integer if necessary. A stochastic division is also possible. Revised Text: p 264, 3rd-last para, before: A CommunicationStep defines the conveyance of a message between system entities, and has an attribute of the message size. after: A CommunicationStep defines the conveyance of a message between system entities, and has an attribute of the message size. The repetitions attribute of a CommunicationStep Inherited from Step) denotes multiple sendings (event multiplication) if >1, or decimation of sendings (event division) if <1. If repetitions is deterministic and less than 1 it is interpreted as event division by N = 1/repetitions, rounded to the nearest integer. That is, every Nth execution of the sending Step causes on cal to occur. Repetitions may also be a random quantity. Actions taken: December 7, 2007: received issue February 17, 2010: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 07 Dec 2007 08:59:36 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Dr. Huascar Espinoza Company: CEA LIST mailFrom: huascar.espinoza@cea.fr Notification: Yes Specification: UML Profile for MARTE Section: GQAM FormalNumber: ptc/07-08-04 Version: Beta 1 RevisionDate: 08/04/07 Page: 263 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1) Description [GQAM: Domain Model & Profile] The PrecedenceRelation concept (fig 15.3) could be used to specify delays due to e.g., queues. However, PrecedenceRelation only exists in the Domain Model. Its implementation is intended to be supported by existing UML concepts (e.g., forks, joints, etc.) I.d suggest to define the corresponding stereotype (<>) in order to allow for modelling delays or other precedence patterns like event divisors: a number of event occurrences triggers an execution. Date: Wed, 13 Feb 2008 17:00:08 -0500 (EST) From: Murray Woodside Reply-To: cmw@sce.carleton.ca To: issues@omg.org Subject: issue 11774 -- MARTE FTF: propose to drop This enhancement is not necessary, since everything it would provide can already be done and in a more consistent way. Since a precedence relation always leads to one or more steps, the queueing etc can be attached to the step. In fact it is essential to do that because it is the step that waits. For example, a fork precedence would have a different waiting on each branch of the fork, which would be complex to describe or specify within the fork, but very easy on the following steps. An event divisor or multiplier could be provided using the Step stereotype. A call can be stereotyped as a CommStep, and has a repetition attribute. ( I know this is true in PAM at least). If this is set to N, it means the call is repeated N times, giving multiplication. If it is set to 1/N, it means that every Nth execution of the sender gives a call... an event divisor. The document could be edited to make this interpretation clear and formal. The repetition count can in principle be a random quantity... if specified as deterministic and <1, it would bear the interpretation of exactly once in N. N could be rounded, for cases where 1/N doesnt have an exact decimal representation. Murray Woodside ---------- * Name: Dr. Huascar Espinoza * Company: CEA LIST * mailFrom: huascar.espinoza@cea.fr * Notification: Yes * Specification: UML Profile for MARTE * Section: GQAM * FormalNumber: ptc/07-08-04 * Version: Beta 1 * RevisionDate: 08/04/07 * Page: 263 * Nature: Enhancement * Severity: Significant * HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; InfoPath.1) Description [GQAM: Domain Model & Profile] The PrecedenceRelation concept (fig 15.3) could be used to specify delays due to e.g., queues. However, PrecedenceRelation only exists in the Domain Model. Its implementation is intended to be supported by existing UML concepts (e.g., forks, joints, etc.) I'd suggest to define the corresponding stereotype (<>) in order to allow for modelling delays or other precedence patterns like event divisors: a number of event occurrences triggers an execution. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org