I'm trying to design a UML class diagram that represents Users that interact with other classes based on their roles, I've chosen to represent Roles as an enum class like so :
What i'd like to represent is that only a user with a Role ADMIN can create a project, only a MANAGER can modify it and every CONSULTANT can only participate in it, can this be achievable with enum representation for Roles?
Being an enumeration RoleName is better drawn with <<enumeration>> (like in the Figure 7.1 - Class Diagram Example page 7 of Object Constraint Language - formal/2014-02-03 )
If Role is only an envelop for RoleName that class is useless (this is what I suppose in the diagram below)
The relations create, manage, participate do not represent attributes, the multiplicities have non sense in that context. The relation role has the default multiplicity 1
Your constraints are pre-conditions, their context is the class User and in OCL the equality operator is "=", so your diagram can be :
You are mixing static representation and behavior. The User has one association to Project (not 3 different ones):
The different behavior (derived from some UC) can be shown in a collaboration. E.g. in an AD like this:
Just a sketch, but that should give you the gist.
