Issue 17032: Ambiguous mulitplicity of Target::CommunicationPath::connectedNode (deployment-rtf)
Source: Fraunhofer FOKUS (Mr. Max Bureck, max.bureck(at)fokus.fraunhofer.de)
Nature: Clarification
Severity: Minor
Summary: The multiplicity of stereotype-property Target::CommunicationPath::connectedNode is [1..*] in the overview picture, in textual description it is [*]. The multiplicity of [1..*] makes more sense, since the source for the derived property is 
self.interconnect.connectedNode, where CommunicationPath::interconnect has multiplicity [1..*] and Interconnect::connectedNode has multiplicity [1..*], so there should be at least one connectedNode.
Resolution: 
Revised Text: 
Actions taken:
January 23, 2012: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Max Bureck
Employer:        Fraunhofer FOKUS
mailFrom:        max.bureck@fokus.fraunhofer.de
Terms_Agreement: I agree
Specification:   Deployment and Configuration of Component-based Distributed Applications Specification
Section:         8.3.2.3
FormalNumber:    formal/2006-04-02
Version:         4.0
Doc_Year:        2006
Doc_Month:       April
Doc_Day:         02
Page:            108; 109
Title:           Ambiguous mulitplicity of Target::CommunicationPath::connectedNode
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


The multiplicity of stereotype-property Target::CommunicationPath::connectedNode is [1..*] in the overview picture, in textual description it is [*]. The multiplicity of [1..*] makes more sense, since the source for the derived property is 
self.interconnect.connectedNode, where CommunicationPath::interconnect has multiplicity [1..*] and Interconnect::connectedNode has multiplicity [1..*], so there should be at least one connectedNode.