Figure 1P-21 - PolicyApplication Subclasses : Class diagram
Created: |
3/28/2022 3:51:09 PM |
Modified: |
6/9/2022 4:09:21 PM |
Project: |
|
Author: |
broth |
Version: |
22.0 |
Advanced: |
|
ID: |
{F6BA1660-AABB-489f-B4CF-FE4CDB15125A} |
The PolicyApplication class is used as a convenient point for defining relationships to different managed entities. It has four principal subclasses: PolicyServer, PolicyDecisionPoint (PDP), PolicyExecutionPoint (PXP) and PolicyEnforcementPoint (PEP). <br/>Figure below has been simplified by removing all relationships except the ContainsPolicyApps aggregation. The OCL expression shown in the ContainsPolicyApps aggregation ensures that a PolicyServer has at least one or more PolicyDecisionPoints, PolicyExecutionPoints, and PolicyEnforcementPoints. This is the minimum amount of functionality required to specify a PolicyServer. Note that a PolicyServer can have additional functionality specified; however, that is only relevant in the system view, and hence will not be discussed further in this document.<br/>