File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
OO, Patterns, UML and Refactoring
Composite relationship and 0..1 multiplicity
Joined: Jan 26, 2011
Oct 03, 2011 13:54:51
Can somebody explain me how the composite relationship and the 0..1 multiplicity can coexist together? Let's see at the attachment: EncapsulatedClassifier - Port relationship (from UML 2.1 spec):
EncapsulatedClassifier is a structured classifier
Port is a Property
Property is a part of StructuredClassifier
It means to me that Port can not exist without a EncapsulatedClassifier as its part
So - What the
in 0..1 multiplicity means? In my current understanding of this only
multiplicity would be correct...
Joined: Mar 10, 2008
Oct 04, 2011 08:32:04
I agree with you that is looks a bit strange.
The only explanation I can come up with is if we have all the Ports in a pool so that we can define all ports but not assign them to an EncapsulatedClassifyer. But it still looks strange.
I agree. Here's the link:
subject: Composite relationship and 0..1 multiplicity
Java Coding and UML Aggregation v/s Composition
IBM 158 Problem
long post IBM.158
What does this symbol indicate?
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014