Issue 6875: Components / provided and required interfaces -- derived or subsets (uml2-superstructure-ftf)
Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org)
Nature: Uncategorized Issue
Severity: 
Summary: Should Component::provided and Component::required really be derived? It seems that these sets of interfaces should be subsets of the sets of interfaces implemented/used by the component and/or its realizing classifiers, not derived from them
Resolution: 
Revised Text: 
Actions taken:
January 2, 2004: received issue
March 9, 2005: closed issue
Discussion: 
[After discussion with the submitter] The above solution would apply if a component
could only expose interfaces through Impleme ntation relationships. However, a
derivation is appropriate because there are 3 ways in which a component can provide an
interface (analogous arguments hold for required interfaces):
The provided interfaces of a component are those interfaces that are
a. implemented by the component or
b those typing its provided ports
c. those interfaces exposed by internal elements (if no interfaces are defined on the
component itself)
This derivation has been formalized in OCL as part of issue 6315.
Disposition: Closed, no change
End of Annotations:=====
ubject: UML 2 Super / Components / provided and required interfaces -- derived or 
 subsets 
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 
From: Branislav Selic <bselic@ca.ibm.com> 
Date: Fri, 2 Jan 2004 07:41:39 -0500 
X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 6.0.2CF1|June 9, 2003) at 
 01/02/2004 07:41:40, 
        Serialize complete at 01/02/2004 07:41:40 


Should Component::provided and Component::required really be derived? It seems that these sets of interfaces should be subsets of the sets of interfaces implemented/used by the component and/or its realizing classifiers, not derived from them. 

Bran Selic
Distinguished Engineer
IBM Rational Software