Figure SO.26 - Grouping Together CustomerFacingServiceSpecifications into a ServicePackage

<font color="#29313b">For example, GoldPackageSpec is an individual packaging of services, and is therefore an instance of the ServicePackageSpecAtomic class. If there was a service offering that combined the services defined by the GoldPackageSpec with those defined by the PlatinumPackageSpec, then that would be an instance of the ServicePackageSpecComposite class.</font><br/><font color="#29313b">Figure SO.25 shows five exemplary subclasses of the ServicePackageSpecAtomic class – PlatinumPackageSpec, GoldPackageSpec, SilverPackageSpec, BronzePackageSpec, and BestEffortPackageSpec. Ignoring the latter for the moment, each of these classes represents a collection of CustomerFacingServiceSpecs that work together to collectively offer a set of Services. This enables these Services to be compared as a group to (for example) a ServiceLevelAgreement.  Conceptually, this can be represented as shown in Figure SO.26. </font><br/><font color="#29313b">There are two important differences between Platinum, Gold, Silver, and Bronze Service. The first is obvious from Figure SO.26 – the better the Service Level, the more CustomerFacingServices that a user has access to. The second is more subtle, and involves the quality of CustomerFacingService. For example, all four ServicePackages above provide Web and Data access. The difference between these applications is that the quality of Web and Data access for PlatinumService is better from an end-user’s point-of-view (i.e., faster downloads, less waiting, etc.) than that for GoldService, and so forth.</font><br/><br/>