Consider the following (abstract) situation:

Two entities. There are two aggregation relationships between the two entities.

The diagram looks like this:

Two aggregation relationships

I know this might sound vague, but is there anything wrong with this picture?

I mean, are there any (obvious) problems that could arise from this kind of design?

Or am I being paranoid and there's absolutely nothing wrong with two (or more) aggregation relationships between two entities?

有帮助吗?

解决方案

For me there is nothing wrong in such design. Your Entity2 will have a different role in each context that's all.

其他提示

Nothing wrong with the diagram. Here is a more meaningful example. Diagram

-Kenji

As long as the relationships are fulfilling really different roles (as you indictated by the numbering) I think it is a good approach, as you make them explicit.

Otherwise you could make use of the cardinality:

Cardinality

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top