When to use memberEnd and when navigableOwnedEnd in an UML class diagram?

Posted by Ivan on Stack Overflow See other posts from Stack Overflow or by Ivan
Published on 2010-05-23T10:35:39Z Indexed on 2010/05/23 12:10 UTC
Read the original article Hit count: 265

Filed under:
|
|
|
|

I've download a trial of Altova UModel and am starting using UML. As a practical beginning I am modelling a personal information manager application, which includes a web bookmark managing.

A Bookmark can belong to many (or no) Tags at once and a Tag can contain many (or no if all the bookmarks it contained were deleted) bookmarks. The relation has to be both-way navigable - a user has to be able to see all Bookmarks with a particular Tags ans all Tags of a Bookmark.

What is the correct UML relation between Bookmark and Tag classes?

As far as I understand UML now, it is an Association (not an Aggregation). But for a 2-way navigable many-to-many relation I can specify ends roles as "memberEnd" or "when navigableOwnedEnd", graphically the connection looks the same in both cases (an arrow) (which as I understand means navigability) but a property appears in the class box in case only when "memberEnd" is used.

How should I specif it in the model If I mean both-way navigable many-to-many relation there?

© Stack Overflow or respective owner

Related posts about class

Related posts about uml