Issue 15291: ImpliesConstraint of Allocate and Assign relationships (marte-rtf) Source: Airbus Group (Mr. Yves Bernard, yves.bernard(at)airbus.com) Nature: Uncategorized Issue Severity: Summary: According to its definition, the impliesConstraint association of both Allocate and Assign stereotypes should be a composition and not a simple reference Resolution: Revised Text: Actions taken: June 16, 2010: received issue Discussion: End of Annotations:===== m: "BERNARD, Yves" To: "issues@omg.org" Date: Wed, 16 Jun 2010 15:32:02 +0200 Subject: [MARTE] - ImpliesConstraint of Allocate and Assign relationships Thread-Topic: [MARTE] - ImpliesConstraint of Allocate and Assign relationships Thread-Index: AcsNWE3W+iWgkSCZTXWwQe2WXF0GOQ== Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-OriginalArrivalTime: 16 Jun 2010 13:32:04.0063 (UTC) FILETIME=[4ECE7EF0:01CB0D58] Juerguen, Would you give a number for the following issue, please? According to its definition, the impliesConstraint association of both Allocate and Assign stereotypes should be a composition and not a simple reference Thanks, Yves The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. From: GERARD Sebastien 166342 To: "marte-rtf@omg.org" Subject: MARTE 1.2 RTF: issue 15291 Thread-Topic: MARTE 1.2 RTF: issue 15291 Thread-Index: AcyDdxj4ajSSJ4NFQCGNWHzZ6rO1Wg== Date: Wed, 5 Oct 2011 15:54:43 +0000 Accept-Language: fr-FR, en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [132.166.88.106] x-tm-as-product-ver: SMEX-10.0.0.4152-6.800.1017-18426.007 x-tm-as-result: No--43.675300-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Hi all, I have uploaded a resolution for the issue 15291 on the wiki. Cheers. Sé ------------------------------------------------------------------------------------------------------------------------------------------------ Sésten Gérd CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE), Point Courrier 94, Gif-sur-Yvette, F-91191 France www.eclipse.org/papyrus From: "BERNARD, Yves" To: Frederic Mallet CC: "marte-rtf@omg.org" Date: Mon, 17 Oct 2011 17:15:41 +0200 Subject: RE: MARTE 1.2 RTF: issue 15291, Alloc_wg Thread-Topic: MARTE 1.2 RTF: issue 15291, Alloc_wg Thread-Index: AcyHY9pwqW46kKxsTtyZoPNIjSGMMAFeWOuA Accept-Language: fr-FR, en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US Hi Frederic, The issue summary doesn.t say that it is an aggregation. Refer to the description of the Allocate extension: .The purpose of the impliedConstraint association is to explicitly identify what are the constraints that only apply if or when the allocation is performed.. Since .the constraint only apply when the allocation is performed. it means that the constraint shall be released when it is not performed. The point is that breaking the association between the constraint and the allocation does not remove the constraint from the constrained elements, since the constrainedElement property of the constraint remains unchanged. Anyway there are some errors in this resolution: the name of the association should be .impliedConstraint. and not .impliesConstraint. or .impliedConstraints. as written in the issue document. Yves From: Frederic Mallet [mailto:Frederic.Mallet@inria.fr] Sent: lundi 10 octobre 2011 17:47 To: BERNARD, Yves Cc: GERARD Sebastien 166342; marte-rtf@omg.org Subject: Re: MARTE 1.2 RTF: issue 15291, Alloc_wg Yves, I do not understand your point here. First, it is not an aggregation right now but a mere association. Second, replacing by a composition just reduces the expressivity without bringing any real added value. For instance, you cannot share constraints with a composition. I am not saying you often need to, but why would you prevent the users from doing so. The allocation and assign are meant to be generic enough to cover several usages. I would prefer not to replace by a composition. I suggest we take the time of the discussion period (until October 23rd) to get an agreement on that. I would rather have instead "ClosedNoChange". BTW, have you made any progress on the allocation within the UML RTF ? Fréric. Le 05/10/2011 17:54, GERARD Sebastien 166342 a éit : Hi all, I have uploaded a resolution for the issue 15291 on the wiki. Cheers. Sé ------------------------------------------------------------------------------------------------------------------------------------------------ Sésten Gérd CEA LIST, Laboratoire d.Ingéerie dirigépar les modès pour les Systès Embarqué(LISE), Point Courrier 94, Gif-sur-Yvette, F-91191 France www.eclipse.org/papyrus This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.