Project:
|
![]() Figure SO.12 - Modeling Stand-Alone and Aggregate Services : Class diagram
Similarly as specification part, CustomerFacingService and ResourceFacingService both use the same composite pattern. The difference is that since Services are in reality instances defined by a ServiceSpecification, the atomic and composite services are melded into CustomerFacingServices and ResourceFacingServices. In other words, generic Services are CustomerFacingServices and ResourceFacingServices themselves. While other types of Services could certainly be defined, their associated ServiceSpecification needs to be defined first. The following Figure shows the composite pattern applied to CustomerFacingServices and ResourceFacingServices.<br/>
|