Figure SO.13 - Modeling the Versioning of a ServiceSpecification

Applications often require the ability to distinguish between different versions of objects in general. This Addendum applies this principal to ServiceSpecifications. The ServiceSpecVersion class represents a particular form or variety of a ServiceSpecification that is different from others or from the original.  The form represents differences in attributes, relationships, and/or constraints that characterize this particular ServiceSpecification, but which are not enough to warrant creating a new ServiceSpecification.<br/>The CustomerFacingServiceSpecVersion and ResourceFacingServiceSpecVersion subclasses are defined to enable an application to track different versions of CustomerFacingServiceSpecs and ResourceFacingServiceSpecs independently.<br/>The ServSpecModifications aggregation represents the set of versions of this ServiceSpecification. The semantics of this aggregation are implemented with the ServiceSpecVersionDetails class.<br/>The two version details association classes are both derived from the ServSpecModifications aggregation. They add additional detail to the generic concept of defining a version of a ServiceSpecification.<br/>The same exact principle applies to tracking different versions of the more generic ServiceSpecAtomic and ServiceSpecComposite objects. This is not shown because the focus of this Addendum is on the definition of CustomerFacingServices and ResourceFacingServices.<br/>