Firstly, I'd like to thank those who answered my previous question ages ago. Currently I'm engaging more in the design phase UMLs, as this is my first medium scale deployment I'm entrusted with.
This is extremely simple, but it bugs me so.
If (Component) owns (Manager of Component), and (Manager of Component) has a reference to (Component) through which it manages it; 开发者_运维问答how do you fully describe the relationship?
I know it is aggregative, but how do you describe (Manager of Component) possessing a reference/pointer to the (Component) that physically owns the (Manager of Component) ?
Example: Lidar owns a LidarManager
On first sight, it seems a little strange for Component
to own Manager of Component
. Would expect it the other way around. Anyway, assuming you need it this way...
...it's just a plain old aggregation relationship, navigable in both directions, with diamond at Component
end.
hth.
精彩评论