{{#reviewabout:Submissions:Inverse n-ary relationship|}}

ODPUser.png
Review Summary: This pattern express that an n-ary relationship (OffersServiceAtPlaceTimeWithPrice) can be summarize in a simple relationship (provideService property) between the two main participants (ServiceProvider and Service).

The relationship between the two main participants can be modelized with different details (rought modelization and detailed one).

The purpose of this pattern is to make the querying of the knowledge based more easy. But you will have to manage the updating of the knowledge base. The simple relation may exist even if the n-ary relationship do not...and vice versa...So if there is no problem with that point I am OK... Maybe you could explain that the creation of the simple relationship can be derived from the existence of the n-ary relationship.
Reviewer Confidence:
Problems:
Community Relevance:
Relation to Best Practices:
Reusability:
Relations to Other Patterns:
Overall Understandability:
Clear Problem Description:
Clear Relevance and Consequences:
Clear Figures and Illustrations:
Missing Information:

Posted: 2010-09-10 Last modified: 2010/09/10

All reviews | Add a comment at the bottom of this page
The page [[Bootstrap:Footer]] was not found.