Issue 13395: UML2: Unclear how to indicate what events a classifier might send (uml2-rtf) Source: International Business Machines (Mr. Jim Amsden, jamsden(at)us.ibm.com) Nature: Uncategorized Issue Severity: Summary: UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received Resolution: Revised Text: Actions taken: January 30, 2009: received issue Discussion: End of Annotations:===== ubject: UML2: Unclear how to indicate what events a classifier might send X-KeepSent: 199D1524:940ED6F0-8525754E:005A3687; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 11:40:14 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 09:40:14, Serialize complete at 01/30/2009 09:40:14 UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM Subject: RE: issue 13395 -- UML 2 RTF issue Date: Fri, 30 Jan 2009 13:26:29 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 13395 -- UML 2 RTF issue thread-index: AcmC/NdRcIl5z1BnTOayHmgs9UjvcAAChnyA From: "Ed Seidewitz" To: Jim . I am not sure what the issues is here. Clearly, if an interface can have receptions, then a classifier could use/require such an interface, which would seem to already mean that the classifier intends to send signals to be received by something conforming to the used/required interface. Further, it is possible to target a send signal action via a port (through the extension to InvocationAction specified in 9.3.9), which would presumably be send a signal through the required interface of the port. Finally, the definition of Port::required (in 9.3.11) is: required: Interface . References the interfaces specifying the set of operations and receptions that the classifier expects its environment to handle. This association is derived as the set of interfaces required by the type of the port or its supertypes. So, what update are you looking for in the spec? -- Ed -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Friday, January 30, 2009 12:00 PM To: issues@omg.org; uml2-rtf@omg.org Subject: issue 13395 -- UML 2 RTF issue To: issues@omg.org Subject: UML2: Unclear how to indicate what events a classifier might send X-KeepSent: 199D1524:940ED6F0-8525754E:005A3687; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 11:40:14 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 09:40:14, Serialize complete at 01/30/2009 09:40:14 UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 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 To: uml2-rtf@omg.org Subject: RE: issue 13395 -- UML 2 RTF issue X-KeepSent: 02817E85:5FAD37AD-8525754E:00764A42; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 16:43:30 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 14:43:31, Serialize complete at 01/30/2009 14:43:31 Ed, Agree no change is needed to the metamodel. But I don't think the spec currently describes what it means to require/use an interface that contains a reception. It only describes the meaning of a reception in a provided/realized interface - that the realizing classifier is able to receive the associated signal. So this is just a clarification in the spec to make sure the send and receive sides are both described. The spec should also recommend that any signal a classifier is able to send (in any of its behaviors) should be described by a reception in some required interface. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 From: "Ed Seidewitz" To: Date: 01/30/2009 01:30 PM Subject: RE: issue 13395 -- UML 2 RTF issue -------------------------------------------------------------------------------- Jim .> I am not sure what the issues is here. Clearly, if an interface can have receptions, then a classifier could use/require such an interface, which would seem to already mean that the classifier intends to send signals to be received by something conforming to the used/required interface. Further, it is possible to target a send signal action via a port (through the extension to InvocationAction specified in 9.3.9), which would presumably be send a signal through the required interface of the port. Finally, the definition of Port::required (in 9.3.11) is: required: Interface . References the interfaces specifying thee set of operations and receptions that the classifier expects its environment to handle. This association is derived as the set of interfaces required by the type of the port or its supertypes. So, what update are you looking for in the spec? -- Ed -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Friday, January 30, 2009 12:00 PM To: issues@omg.org; uml2-rtf@omg.org Subject: issue 13395 -- UML 2 RTF issue To: issues@omg.org Subject: UML2: Unclear how to indicate what events a classifier might send X-KeepSent: 199D1524:940ED6F0-8525754E:005A3687; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 11:40:14 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 09:40:14, Serialize complete at 01/30/2009 09:40:14 UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 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 Subject: RE: issue 13395 -- UML 2 RTF issue Date: Fri, 30 Jan 2009 17:53:01 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 13395 -- UML 2 RTF issue thread-index: AcmDJBfp5vWMik47QymmtdQQeGGFAwACNRjg From: "Ed Seidewitz" To: Jim . Well, I don.t think the spec says much about what it means to require/use an interface with operations and attributes, either. All it really says in 7.3.24 is .Required interfaces specify services that a classifier needs in order to perform its function and fulfill its own obligations to its clients.. Are you proposing to add semantics text to 13.3.35, which specifies the ability of interfaces to have receptions? This might be a reasonable idea, but I think that you would then also want to say a bit more about operations under 7.3.24. It would be a bit strange to have more semantics on the usage of receptions in interfaces than operations, since the latter is still the more common (and basic) case. Or am I missing somewhere else in the spec where this is discussed? -- Ed -------------------------------------------------------------------------------- From: Jim Amsden [mailto:jamsden@us.ibm.com] Sent: Friday, January 30, 2009 4:44 PM To: uml2-rtf@omg.org Subject: RE: issue 13395 -- UML 2 RTF issue Ed, Agree no change is needed to the metamodel. But I don't think the spec currently describes what it means to require/use an interface that contains a reception. It only describes the meaning of a reception in a provided/realized interface - that the realizing classifier is able to receive the associated signal. So this is just a clarification in the spec to make sure the send and receive sides are both described. The spec should also recommend that any signal a classifier is able to send (in any of its behaviors) should be described by a reception in some required interface. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 From: "Ed Seidewitz" To: Date: 01/30/2009 01:30 PM Subject: RE: issue 13395 -- UML 2 RTF issue -------------------------------------------------------------------------------- Jim . I am not sure what the issues is here. Clearly, if an interface can have receptions, then a classifier could use/require such an interface, which would seem to already mean that the classifier intends to send signals to be received by something conforming to the used/required interface. Further, it is possible to target a send signal action via a port (through the extension to InvocationAction specified in 9.3.9), which would presumably be send a signal through the required interface of the port. Finally, the definition of Port::required (in 9.3.11) is: required: Interface . References the interfaces specifying the set of operations and receptions that the classifier expects its environment to handle. This association is derived as the set of interfaces required by the type of the port or its supertypes. So, what update are you looking for in the spec? -- Ed -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Friday, January 30, 2009 12:00 PM To: issues@omg.org; uml2-rtf@omg.org Subject: issue 13395 -- UML 2 RTF issue To: issues@omg.org Subject: UML2: Unclear how to indicate what events a classifier might send X-KeepSent: 199D1524:940ED6F0-8525754E:005A3687; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 11:40:14 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 09:40:14, Serialize complete at 01/30/2009 09:40:14 UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 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 To: uml2-rtf@omg.org Subject: RE: issue 13395 -- UML 2 RTF issue X-KeepSent: C7179DFC:A287BAFD-85257550:00448C88; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Sun, 1 Feb 2009 07:33:40 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 02/01/2009 05:33:41, Serialize complete at 02/01/2009 05:33:41 Ed, That's really what I was looking for. We all pretty much understand what it means to have a required interface with an operation - it means the requiring classifier is going to call those operations sometime and the connected parties would need to provide them. This is less clear with signals, receptions, triggers, events, and send and accept actions simply because of the complex conceptual and metamodel path. I just thought this could use some clarification as receptions are never mentioned in required interfaces that I know of. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 From: "Ed Seidewitz" To: Date: 01/30/2009 06:02 PM Subject: RE: issue 13395 -- UML 2 RTF issue -------------------------------------------------------------------------------- Jim . Well, I don..t think the spec says much about what it means to require/use an interface with operations and attributes, either. All it really says in 7.3.24 is ..Required interfaces specify services that a classifier needs in order to perform its function and fulfill its own obligations to its clients.. Are you proposing to add semantics text to 13.3.35, which specifies the ability of interfaces to have receptions? This might be a reasonable idea, but I think that you would then also want to say a bit more about operations under 7.3.24. It would be a bit strange to have more semantics on the usage of receptions in interfaces than operations, since the latter is still the more common (and basic) case. Or am I missing somewhere else in the spec where this is discussed? -- Ed -------------------------------------------------------------------------------- From: Jim Amsden [mailto:jamsden@us.ibm.com] Sent: Friday, January 30, 2009 4:44 PM To: uml2-rtf@omg.org Subject: RE: issue 13395 -- UML 2 RTF issue Ed, Agree no change is needed to the metamodel. But I don't think the spec currently describes what it means to require/use an interface that contains a reception. It only describes the meaning of a reception in a provided/realized interface - that the realizing classifier is able to receive the associated signal. So this is just a clarification in the spec to make sure the send and receive sides are both described. The spec should also recommend that any signal a classifier is able to send (in any of its behaviors) should be described by a reception in some required interface. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 From: "Ed Seidewitz" To: Date: 01/30/2009 01:30 PM Subject: RE: issue 13395 -- UML 2 RTF issue -------------------------------------------------------------------------------- Jim . I am not sure what the issues is here. Clearly, if an interface can have receptions, then a classifier could use/require such an interface, which would seem to already mean that the classifier intends to send signals to be received by something conforming to the used/required interface. Further, it is possible to target a send signal action via a port (through the extension to InvocationAction specified in 9.3.9), which would presumably be send a signal through the required interface of the port. Finally, the definition of Port::required (in 9.3.11) is: required: Interface . References the interfaces specifying the sset of operations and receptions that the classifier expects its environment to handle. This association is derived as the set of interfaces required by the type of the port or its supertypes. So, what update are you looking for in the spec? -- Ed -------------------------------------------------------------------------------- From: Juergen Boldt [mailto:juergen@omg.org] Sent: Friday, January 30, 2009 12:00 PM To: issues@omg.org; uml2-rtf@omg.org Subject: issue 13395 -- UML 2 RTF issue To: issues@omg.org Subject: UML2: Unclear how to indicate what events a classifier might send X-KeepSent: 199D1524:940ED6F0-8525754E:005A3687; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 From: Jim Amsden Date: Fri, 30 Jan 2009 11:40:14 -0500 X-MIMETrack: Serialize by Router on D03NM118/03/M/IBM(Release 8.5|December 05, 2008) at 01/30/2009 09:40:14, Serialize complete at 01/30/2009 09:40:14 UML2 has Receptions which can be included in realized/provided Interfaces to indicate what Signal events a Classifier is able to receive. But it isn't clear how a Classifier would indicate in its interfaces what events it might send/generate, and therefore what events a collaborating Classifier connected to this Classifier in some way would need to be prepared to handle. UML2 Reception semantics should be updated to indicate Receptions can appear in either Realized/provided or Usage/required Interfaces. A Reception in a required interface would indicate a signal event the owning classifier might send through a SendSignalAction or BroadcastSignalAction. This would provide all the interface information needed on both sides of a connector to know what SignalEvents might be sent and/or received. Jim Amsden STSM, Solution Architect jamsden@us.ibm.com Jim Amsden/Raleigh/IBM 919-461-3919 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 919-461-3919