Reputation: 839
I have a parameter table and I want to model it in a class diagram. Should we put such a parameter table in a class diagram ? What does this table represent exactly ? an enumeration or what ? should i model it as an enumeration class ?
This is my diagram :
The table "Droit" is a parameter table. Is my model correct ?
Edit: The diagram is French. "Profil" and "Droit" means "Profile" and "Rights". "Libelle" means "Description". And "Ajouter", "Modifier", "Consulter" means "Add", "Change", "View".
Upvotes: 0
Views: 301
Reputation: 73530
It seems that your whole entity-control-boundary class diagram is about management of (user?) profiles. It seems furthermore that your entity Droit
represents the authorization rights that a Profil
may have.
If these hypotheses are confirmed, I'd think that Droit
should be fully part of this diagram. It would be difficult to understand the structure of profiles and implement the controller methods without knowledge of this information.
The fact that you consider this table as a "parameter table" is not relevant here. The main question is not the importance of the class to the overall system but what you want to represent in your diagram. If it's a zoom on profiles & authorisation management, you'll need it. Of couse, would your model be focused on business classes, where such a a table wouldn't add to the understanding of the domain, would my answer be different.
Upvotes: 1