Issue 18676: ProxyPort with FlowProperties (sysml-rtf) Source: oose Innovative Informatik eG (Mr. Tim Weilkiens, tim.weilkiens(at)oose.de) Nature: Uncategorized Issue Severity: Summary: I struggle to use proxy port with flow properties. One idea is to use a behavioral port and to bind the flow properties with the behavior parameters. In chapter 9.3.2.7 about FlowProperties the spec states: The binding of flow properties on ports to behavior parameters can be achieved in ways not dictated by SysML. One approach is to perform name and type matching. Another approach is to explicitly use binding relationships between the ports properties and behavior parameters or block properties. What are port properties? A port has no properties, but the type of the port, e.g. a InterfaceBlock. And these properties are the same for any usage of the InterfaceBlock and I can’t use context-specific binding relationships. Resolution: Defer Postponed to the next RTF Revised Text: Actions taken: April 18, 2013: received issue January 3, 2017: Deferred April 6, 2017: closed issue Discussion: End of Annotations:===== m: Tim Weilkiens To: "Sysml-Rtf (sysml-rtf@omg.org)" Subject: ProxyPort with FlowProperties Thread-Topic: ProxyPort with FlowProperties Thread-Index: Ac47X+z8TprGoUVcSkuFwENSGGhaBg== Date: Thu, 18 Apr 2013 07:02:29 +0000 Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.19] X-XWALL-BCKS: auto X-Virus-Scanned: amavisd-new at omg.org Hi, I struggle to use proxy port with flow properties. One idea is to use a behavioral port and to bind the flow properties with the behavior parameters. In chapter 9.3.2.7 about FlowProperties the spec states: The binding of flow properties on ports to behavior parameters can be achieved in ways not dictated by SysML. One approach is to perform name and type matching. Another approach is to explicitly use binding relationships between the ports properties and behavior parameters or block properties. What are port properties? A port has no properties, but the type of the port, e.g. a InterfaceBlock. And these properties are the same for any usage of the InterfaceBlock and I can.t use context-specific binding relationships. Tim Tim Weilkiens (CEO) oose Innovative Informatik GmbH Kontorhaus Montblanc, Schulterblatt 36, D-20357 Hamburg, Germany HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 CEO Tim Weilkiens Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 Internet: www.oose.de, E-Mail: info@oose.de From: "BERNARD, Yves" To: Tim Weilkiens , "Sysml-Rtf (sysml-rtf@omg.org)" Date: Thu, 18 Apr 2013 10:04:05 +0200 Subject: RE: ProxyPort with FlowProperties Thread-Topic: ProxyPort with FlowProperties Thread-Index: Ac47X+z8TprGoUVcSkuFwENSGGhaBgAqGV4g Accept-Language: fr-FR, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: fr-FR, en-US X-Virus-Scanned: amavisd-new at omg.org Hi Tim, There are two points in your question. The first point is about the link between flow properties specified by the type of a behavior port and the parameters of the classifier behavior of the owner of this port. It is an issue that is still pending. We still haven.t had an in-deep discussion on this subject. I.m in favor of opening it now if we can gather the .critical mass. on it. Your second point is about ports. properties. Ports do have properties, as defined by their metaclasse. Among them there is the .type. property specifying the type of the interaction point represented by that port. This type specifies the property of the owner of the port that can be accessed at that interaction point. For proxy ports, this type shall be defined by an InterfaceBlock with the same .contract. semantics which is given to an Interface in UML. The actual relationships between the properties specified within a contract and the property of the port.s owner is not clearer in SysML than in UML. This is another clarification we have to work on, in cooperation with the UML 2.5 FTF, I think. Yves From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] Sent: jeudi 18 avril 2013 09:02 To: Sysml-Rtf (sysml-rtf@omg.org) Subject: ProxyPort with FlowProperties Hi, I struggle to use proxy port with flow properties. One idea is to use a behavioral port and to bind the flow properties with the behavior parameters. In chapter 9.3.2.7 about FlowProperties the spec states: The binding of flow properties on ports to behavior parameters can be achieved in ways not dictated by SysML. One approach is to perform name and type matching. Another approach is to explicitly use binding relationships between the ports properties and behavior parameters or block properties. What are port properties? A port has no properties, but the type of the port, e.g. a InterfaceBlock. And these properties are the same for any usage of the InterfaceBlock and I can.t use context-specific binding relationships. Tim Tim Weilkiens (CEO) oose Innovative Informatik GmbH Kontorhaus Montblanc, Schulterblatt 36, D-20357 Hamburg, Germany HRB 66648 Amtsgericht Hamburg, USt-Id DE191433946 CEO Tim Weilkiens Fon: +49 (40) 41 42 50-0, Fax: +49 (40) 41 42 50-50 Internet: www.oose.de, E-Mail: info@oose.de 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: "Bock, Conrad" To: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Fri, 19 Apr 2013 08:58:04 -0400 Subject: RE: ProxyPort with FlowProperties Thread-Topic: ProxyPort with FlowProperties Thread-Index: Ac47X+z8TprGoUVcSkuFwENSGGhaBgBmXh9g Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAh15GpodekU9 X-Brightmail-Tracker: AAAAAA== Tim, > In chapter 9.3.2.7 about FlowProperties the spec states: > The binding of flow properties on ports to behavior parameters can be > achieved in ways not dictated by SysML. One approach is to perform name and > type matching. Another approach is to explicitly use binding relationships > between the ports properties and behavior parameters or block properties. > What are port properties? This is short for the properties on the type of a port. > A port has no properties, but the type of the port, e.g. a > InterfaceBlock. And these properties are the same for any usage of > the InterfaceBlock and I can't use context-specific binding > relationships. Contextualization is in the connector (in partWithPort or NestedConnectorEnd), rather than the port type. > One idea is to use a behavioral port and to bind the flow properties > with the behavior parameters. Nerijus recently suggested having a property of the owning block typed by a behavior. Then binding connectors can link parameters (Parameters are ConnectableElements) to properties on port types. Additional modeling would be needed to assign an instance of the behavior (an execution) to the property typed by the behavior. If the port property is a flow property, the parameter would probably need to be streaming. As part of the work on navigation through non-properties (slides 27 and 28 in http://tinyurl.com/bq88yts) we could add a stereotype of Property requiring it to be typed by the classifierBehavior of the owning block, and have the corresponding execution as a value in instances of that block. Conrad http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Avariant%3Avariants_modeling&cache=cache&media=rtf4:groups:variant:variant-wg-130417a.ppt From: Phil Astle To: "'Bock, Conrad'" , "Sysml-Rtf (sysml-rtf@omg.org)" Subject: RE: ProxyPort with FlowProperties Thread-Topic: ProxyPort with FlowProperties Thread-Index: Ac47X+z8TprGoUVcSkuFwENSGGhaBgBmXh9gAAJz9SA= Date: Fri, 19 Apr 2013 13:46:31 +0000 Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.31.1.39] x-esetresult: clean, is OK x-esetid: B9C0C5236DF93032ED809E X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR15Gpo= X-Brightmail-Tracker: AAAAAA== Conrad, I checked in the UML specification and found the following constraint on the usage of Connectors with Parameters (section 9.3.11 in the UML 2.4 specification): A parameter may only be associated with a connector end within the context of a collaboration. self.end->notEmpty() implies self.collaboration->notEmpty() Wouldn.t this stop you from using them as Nerijus suggested? Phil From: Bock, Conrad [mailto:conrad.bock@nist.gov] Sent: 19 April 2013 13:58 To: Sysml-Rtf (sysml-rtf@omg.org) Subject: RE: ProxyPort with FlowProperties Tim, > In chapter 9.3.2.7 about FlowProperties the spec states: > The binding of flow properties on ports to behavior parameters can be > achieved in ways not dictated by SysML. One approach is to perform name and > type matching. Another approach is to explicitly use binding relationships > between the ports properties and behavior parameters or block properties. > What are port properties? This is short for the properties on the type of a port. > A port has no properties, but the type of the port, e.g. a > InterfaceBlock. And these properties are the same for any usage of > the InterfaceBlock and I can't use context-specific binding > relationships. Contextualization is in the connector (in partWithPort or NestedConnectorEnd), rather than the port type. > One idea is to use a behavioral port and to bind the flow properties > with the behavior parameters. Nerijus recently suggested having a property of the owning block typed by a behavior. Then binding connectors can link parameters (Parameters are ConnectableElements) to properties on port types. Additional modeling would be needed to assign an instance of the behavior (an execution) to the property typed by the behavior. If the port property is a flow property, the parameter would probably need to be streaming. As part of the work on navigation through non-properties (slides 27 and 28 in http://tinyurl.com/bq88yts) we could add a stereotype of Property requiring it to be typed by the classifierBehavior of the owning block, and have the corresponding execution as a value in instances of that block. Conrad http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Avariant%3Avariants_modeling&cache=cache&media=rtf4:groups:variant:variant-wg-130417a.ppt __________ Information from ESET Endpoint Antivirus, version of virus signature database 8245 (20130419) __________ The message was checked by ESET Endpoint Antivirus. http://www.eset.com __________ Information from ESET Endpoint Antivirus, version of virus signature database 8245 (20130419) __________ The message was checked by ESET Endpoint Antivirus. http://www.eset.com From: "Bock, Conrad" To: "Sysml-Rtf (sysml-rtf@omg.org)" Date: Fri, 19 Apr 2013 10:21:42 -0400 Subject: RE: ProxyPort with FlowProperties Thread-Topic: ProxyPort with FlowProperties Thread-Index: Ac47X+z8TprGoUVcSkuFwENSGGhaBgBmXh9gAAJz9SAAAT/lAA== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Virus-Scanned: amavisd-new at omg.org X-Brightmail-Tracker: AAAAAR16RT0= X-Brightmail-Tracker: AAAAAA== Phil, > A parameter may only be associated with a connector end within the context of > a collaboration. > > self.end->notEmpty() implies self.collaboration->notEmpty() > Wouldn't this stop you from using them as Nerijus suggested? Looks like it would. The proposed stereotypes for navigating non-properties will include one for parameters (slide 27 in http://tinyurl.com/bq88yts). This will get around the constraint above by binding properties instead of parameters. Conrad http://www.omg.org/members/sysml-rtf-wiki/lib/exe/fetch.php?id=rtf4%3Agroups%3Avariant%3Avariants_modeling&cache=cache&media=rtf4:groups:variant:variant-wg-130417a.ppt