Non-transferability in Designer
421293Apr 4 2007 — edited Apr 4 2007Hello,
One of the features of Designer over other CASE tools is its ability to support the concept of (non-)transferability between entities.
I've always understood transferability to be non-directional and that it is more sensible (natural) to hold the non-transferability (diamond) symbol at the many end of the relationship which is non-transferable.
I was recently asked to review a logical data model which contained several non-transferable relationships (all 1:M), but every one contained the diamond at both ends of the relationship which I hadn't seen before.
I thought this was incorrect, based on my comments above, but would welcome any feedback.
Thanks,
Antony