Issue 18412: Interactions and parameter assignments (uml25-ftf) Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de) Nature: Revision Severity: Summary: is it intended to not let message arguments being assignable to attributes of the receiving lifeline? As an example: Lifeline A sends a synchronous operation call to Lifeline B for the operation op(in x:Integer). Assume that the Type Lifeline B represents owns a Property p:Integer. The received actual parameter x shall be assigned to Property p of the receiving lifeline. With the current semantics of Messages and its description for notation it is only possible to assign out/inout/return values to a receiving lifeline. Consider the case that a certain Lifeline receives a Signal (no out/inout/return parameter at all) and wants to store the value of an attribute of that Signal in an attribute (either of the surrounding Interaction or its context Classifier); this is not possible by default. In my realm (which is validation and testing mainly using UTP), this is quite normal. A system under test (SUT) responds with a Signal and some values of that signal need to be stored for later calculation or re-sending. Shall we allow this in Interactions? Resolution: Revised Text: Actions taken: February 1, 2013: received issue Discussion: End of Annotations:===== m: "Wendland, Marc-Florian" To: "uml25-ftf@omg.org" Subject: Interactions and parameter assignments Thread-Topic: Interactions and parameter assignments Thread-Index: Ac4A0HZ9KF1OxlHfRbGUPIqjqrvXfg== Date: Fri, 1 Feb 2013 23:50:51 +0000 Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.147.78.77] x-kse-antivirus-interceptor-info: scan successful x-kse-antivirus-info: Clean X-cloud-security-sender: marc-florian.wendland@fokus.fraunhofer.de X-cloud-security-recipient: uml25-ftf@omg.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-gate04-haj2 with 7E5DA794001 X-cloud-security: scantime:.2897 X-Virus-Scanned: amavisd-new at omg.org Hi all, is it intended to not let message arguments being assignable to attributes of the receiving lifeline? As an example: Lifeline A sends a synchronous operation call to Lifeline B for the operation op(in x:Integer). Assume that the Type Lifeline B represents owns a Property p:Integer. The received actual parameter x shall be assigned to Property p of the receiving lifeline. With the current semantics of Messages and its description for notation it is only possible to assign out/inout/return values to a receiving lifeline. Consider the case that a certain Lifeline receives a Signal (no out/inout/return parameter at all) and wants to store the value of an attribute of that Signal in an attribute (either of the surrounding Interaction or its context Classifier); this is not possible by default. In my realm (which is validation and testing mainly using UTP), this is quite normal. A system under test (SUT) responds with a Signal and some values of that signal need to be stored for later calculation or re-sending. Shall we allow this in Interactions? Regards, Marc-Florian Date: Tue, 05 Feb 2013 12:04:24 -0500 From: Tom Rutt User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 To: "Wendland, Marc-Florian" CC: uml25-ftf@omg.org Subject: Re: Interactions and parameter assignments X-Virus-Scanned: amavisd-new at omg.org On 2/1/2013 6:50 PM, Wendland, Marc-Florian wrote: Hi all, is it intended to not let message arguments being assignable to attributes of the receiving lifeline? Marc-Florian: Please file this as a new issue on interactions chapter. It is closely related to other issues we have regarding constraints on messages based on what kind of connectable element the lifeline represents. We can solve all these together. Tom Rutt As an example: Lifeline A sends a synchronous operation call to Lifeline B for the operation op(in x:Integer). Assume that the Type Lifeline B represents owns a Property p:Integer. The received actual parameter x shall be assigned to Property p of the receiving lifeline. With the current semantics of Messages and its description for notation it is only possible to assign out/inout/return values to a receiving lifeline. Consider the case that a certain Lifeline receives a Signal (no out/inout/return parameter at all) and wants to store the value of an attribute of that Signal in an attribute (either of the surrounding Interaction or its context Classifier); this is not possible by default. In my realm (which is validation and testing mainly using UTP), this is quite normal. A system under test (SUT) responds with a Signal and some values of that signal need to be stored for later calculation or re-sending. Shall we allow this in Interactions? Regards, Marc-Florian -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133