Figure P.04c1 - Roles and Permission : Class diagram
Created: |
3/28/2022 3:51:09 PM |
Modified: |
6/8/2022 10:46:08 AM |
Project: |
|
Author: |
broth |
Version: |
22.0 |
Advanced: |
|
ID: |
{01E19215-8630-4db6-A95C-22546F75E4BC} |
PermissionSpecSet specifies a set of permissions that might concern one or many PartyRoleSpecifications. Each PermissionSet may refer to a PermissionSpecSet if it corresponds to applying permissions specified for a PartyRoleSpecification. If PermissionSet corresponds to permissions granted by another PartyRole it has no relationship with a PermissionSpecSet.<br/>Any Entity of the model may enable actions (RootEntityTypeAction). Ex: A Contract (ProductBundle) might be created, updated or removed.<br/>Some actions can be defined on the RootEntityType and not available for a PartyRoleSpecification such as the “change email@” that isn’t available for Users.<br/><i>Note: An action might refer to a business process such as Customer Order Handling</i><br/>ImplicitPermissionSpec defines one or many actions allowed on a type of Entity (RootEntityType). A PermissionSpecSet contains one or many ImplicitPermissionSpec.<br/>When a PartyRole corresponds to a PartyRoleSpec it benefits from all implicit permissions on its own Entities (RootEntity).<br/>A Party playing a role may delegate all or part of his permissions to another Party through ExplicitPermission.<br/>