You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UML has a defined three types of Asscociations between classes, that might be used in class diagramms: Association, Aggregation and Composition.
However, these definitions, concepts and terms are not clearly defined in OOP like mentioned in the Golssary.
Moreover, even worse: There is a general concept of Composition, well known in Math. It means:
If you have an Element x and y, both of type A and you've got an composition operator op, you are able to create a new element z of type A by composing the to elements y and y.
z := x op y!
OOP and UML Classes and so on, suffer from the non existence of an composition operator! That's the reason my we use Components for Architecture and not Classes oder Objects!!
The text was updated successfully, but these errors were encountered:
https://leanpub.com/isaqbglossary/read#Aggregation
https://leanpub.com/isaqbglossary/read#Association
https://leanpub.com/isaqbglossary/read#Composition
I'm totally struggeling with these definitions.
The UML has a defined three types of Asscociations between classes, that might be used in class diagramms: Association, Aggregation and Composition.
However, these definitions, concepts and terms are not clearly defined in OOP like mentioned in the Golssary.
Moreover, even worse: There is a general concept of Composition, well known in Math. It means:
If you have an Element x and y, both of type A and you've got an composition operator op, you are able to create a new element z of type A by composing the to elements y and y.
z := x op y!
OOP and UML Classes and so on, suffer from the non existence of an composition operator! That's the reason my we use Components for Architecture and not Classes oder Objects!!
The text was updated successfully, but these errors were encountered: