Issue 4866: The implementingComposition 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.3 (Composite nodes) 

Description: 
The constraints seem to imply that the implementingComposition association is computed by navigating from FCMCommand to its "performedBy" FCMComponent, then from that to the "instanceOf" FCMType, then from that to an FCMCompositionBinding, and, finally, from that to the FCMComposition. Unfortunately, the association between an FCMCompositionBinding and an FCMType is unidirectional and not navigable from the FCMType back to the FCMCompositionBinding (see Figure 6-1). Further, there may be multiple FCMCompositionBindings for any FCMType (each FCMCompositionBinding is between one FCMType and one FCMComposition, but the model allows more than one binding), so it is not possible to identify a unique, single implementingComposition for an FCMCommand anyway. (Note that this problem becomes immediately apparent if you try to write the constraint in OCL.)

Recommendation: 
If you really want to require each FCMCommand to have an optional "implementingComposition", then I don't think this can be a derived association. And even if you want to constrain the "implementingComposition" to be selected from SOME relevant composition binding, then you need to provide the context for the set of composition bindings to search (or you could use FCMCompositionBindings.allInstances, but this is ugly).

Resolution: 
Revised Text: 
Actions taken:
February 20, 2002: received issue
March 10, 2004: trnsferred to EDOC FTF
Discussion: 
See discussion for issue 4865
End of Annotations:=====
From: Edwin Seidewitz <eseidewitz@intelidata.com>
To: "'uml-eai-ftf@omg.org'" <uml-eai-ftf@omg.org>
Cc: "'issues@omg.org'" <issues@omg.org>, Jean Payne
     <jpayne@intelidata.com>,
   "Igor Teselko (E-mail)"
    <iteselko@homeaccount.com>
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<Od9<pMe9NgD!!
Status: RO


These are some issues from my own review of Chapter 6 (more to
come!). 


Issue: The implementingComposition derived association 
Document: UML Profile and Interchange Models for EAI 
Section: 6.2.3 (Composite nodes) 

Description: 
The constraints seem to imply that the implementingComposition
association is computed by navigating from FCMCommand to its
"performedBy" FCMComponent, then from that to the "instanceOf"
FCMType, then from that to an FCMCompositionBinding, and, finally,
from that to the FCMComposition. Unfortunately, the association
between an FCMCompositionBinding and an FCMType is unidirectional and
not navigable from the FCMType back to the FCMCompositionBinding (see
Figure 6-1). Further, there may be multiple FCMCompositionBindings for
any FCMType (each FCMCompositionBinding is between one FCMType and one
FCMComposition, but the model allows more than one binding), so it is
not possible to identify a unique, single implementingComposition for
an FCMCommand anyway. (Note that this problem becomes immediately
apparent if you try to write the constraint in OCL.)

Recommendation: 
If you really want to require each FCMCommand to have an optional
"implementingComposition", then I don't think this can be a derived
association. And even if you want to constrain the
"implementingComposition" to be selected from SOME relevant
composition binding, then you need to provide the context for the set
of composition bindings to search (or you could use
FCMCompositionBindings.allInstances, but this is ugly).


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" <PHIPPEN@uk.ibm.com> 
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
__________________________