Issue 4867: The representation/parameter derived association (uml-edoc-ftf) Source: Ivar Jacobson International AB (Mr. Ed Seidewitz, eseidewitz(at)ivarjacobson.com) Nature: Uncategorized Issue Severity: Summary: Document: UML Profile and Interchange Models for EAI Section: 6.2.5 (EAITerminal) Description: The representation/parameter association is marked as <<derived>> in Figure 6-6, however no clear description is given on how it is derived. Recommendation: I think the intent is that the terminal represents an FCMParameter of an operation associated with the FCMNode to which the terminal is attached. However, given the associations and navigabilities shown in Figure 6-2, this really cannot be done as a single constraint. Instead, it needs to be done as separate constraints on each kind of FCMNode: FCMFunction: An FCMFunction has FCMTerminals that represent each of the parameters of the FCMOperation invoked by the FCMFunction. (self.interface->select(terminalKind = #in).parameter = self.invokes.inputs) and (self.interface->select(terminalKind = #out).parameter = self.invokes.outputs) and (self.interface->select(terminalKind = #fault).parameter = self.invokes.faults) FCMSource: An FCMSource has a output terminals that represents the input parameters of the operation implemented by the FCMSource. (Note that a source has OUTPUT terminals, but these terminals represent the INPUT parameters within the composition that implements the operation.) (self.interface->forAll(terminalKind = #out)) and (self.interface.parameter = self.implements.inputs) FCMSink: An FCMSink has a single input terminal that represents a single output (or fault) parameter of the operation implemented by the FCMSource associated with the FCMSink. (Note that a source has an INPUT terminal, but this terminal represents an OUTPUT parameter within the composition that implements the operation.) (self.interface->size() = 1) and (self.interface.terminalKind = #in) and self.source.implements.outputs->union(self.source.implements.faults)->includesAll(self.interface) Resolution: Revised Text: Actions taken: February 20, 2002: received issue March 10, 2004: transfreed to EDOC FTF Discussion: See discussion for issue 4865 End of Annotations:===== From: Edwin Seidewitz To: "'uml-eai-ftf@omg.org'" Cc: "'issues@omg.org'" , Jean Payne , "Igor Teselko (E-mail)" Subject: Issues on the UML for EAI Specification (2) Date: Wed, 20 Feb 2002 17:15:39 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1BA5C.20A8DE60" X-UIDL: $QI!!Q> in Figure 6-6, however no clear description is given on how it is derived. Recommendation: I think the intent is that the terminal represents an FCMParameter of an operation associated with the FCMNode to which the terminal is attached. However, given the associations and navigabilities shown in Figure 6-2, this really cannot be done as a single constraint. Instead, it needs to be done as separate constraints on each kind of FCMNode: FCMFunction: An FCMFunction has FCMTerminals that represent each of the parameters of the FCMOperation invoked by the FCMFunction. (self.interface->select(terminalKind = #in).parameter = self.invokes.inputs) and (self.interface->select(terminalKind = #out).parameter = self.invokes.outputs) and (self.interface->select(terminalKind = #fault).parameter = self.invokes.faults) FCMSource: An FCMSource has a output terminals that represents the input parameters of the operation implemented by the FCMSource. (Note that a source has OUTPUT terminals, but these terminals represent the INPUT parameters within the composition that implements the operation.) (self.interface->forAll(terminalKind = #out)) and (self.interface.parameter = self.implements.inputs) FCMSink: An FCMSink has a single input terminal that represents a single output (or fault) parameter of the operation implemented by the FCMSource associated with the FCMSink. (Note that a source has an INPUT terminal, but this terminal represents an OUTPUT parameter within the composition that implements the operation.) (self.interface->size() = 1) and (self.interface.terminalKind = #in) and self.source.implements.outputs->union(self.source.implements.faults)->includesAll(self.interface) Subject: [EAI FTF] New Vote time: Proposed transfer of all issues relating to EAI FTF Section 6.2 To: uml-eai-ftf@omg.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 From: "Rob Phippen" Date: Thu, 24 Apr 2003 18:43:32 +0100 X-MIMETrack: Serialize by Router on D06ML022/06/M/IBM(Release 5.0.9a |January 7, 2002) at 24/04/2003 18:46:49 Dear FTFers, I propose to close all issues relating to "Section 6.2 FCM Derived Associations" of the UML for EAI spec. The issues I raised against the EDOC FTF (and the resolutions to them proposed by Barbara Price) cover the intent of this section, so I propose to reduce section 6.2 to a very brief description that just references the EDOC material. From an 'Issue Disposition' point of view, I am suggesting that we record these issues as 'Transferred to EDOC FTF' (which appears to be a permitted disposition). The issues covered are; 5384 5365 5364 5363 5362 4866 4867 Although the resolution to the EDOC issues has not yet been agreed by the EDOC FTF, I would like to initiate a vote on the 'Transferred' status of theses EAI Issues. Voting deadline: 0900 GMT Thursday 1st May 2003 Regards, Rob. __________________________ Rob Phippen Websphere Platform Messaging Hursley Park, UK Tel. +44 1962 816200 eMail phippen@uk.ibm.com __________________________