Figure D.05 - Links Between Document and Other ABEs

Header Image
Project:
Figure D.05 - Links Between Document and Other ABEs : SID diagram
Created: 2/27/2024 11:59:48 AM
Modified: 6/17/2024 4:20:30 PM
Project:
Advanced:
This is the top of the SID class hierarchy. The purpose of the RootEntity is to define a set of attributes that are common to select SID entities in the Product, Service and Resource domains, such as Service, Service Specification, Resource, and Resource Specification, as well as Policy entities in the Shared domain. These properties enable us to name and describe all objects (manageable and unmanageable) in the environment.<br/><i>Note that six classes shown in the following Figure are abstract. This is because they are all conceptual in nature, and exist in order to organize information and concepts. The name attribute is a generic attribute that enables users of the SID to refer to an object using terminology defined by their application-specific needs. The description attribute is an optional attribute that enables users of the SID to customize the description of a SID object.  The ID attribute provides a unique identity to each entity.</i><br/>A RootEntity might be categorized by a RootEntityType that represents a SID Entity such as Product, ProductSpecification…<br/>A RootEntity might be described by one or many Attachments that refers to a Document or exclusively a DocumentSet such as brochure or manual that can be provided by the Service Provider to Customers when they buy a Product. For example, a contract scan Document might be attached to a ProductOfferingInstance or a manual Document provided by the CSP to the customer during a call attached to the CommunicationInteraction.<br/><font color="#29313b"><br/></font><font color="#29313b">The following subsections will expand on each of the subclasses of RootEntity, except for Collection. Collection represents collections of ManagedEntity objects. This enables common attributes and relationships and other semantics to be applied to different types of Collections of ManagedEntity objects. These can then be refined in the subclasses of Collection. It is currently only used in the Policy ABE (PolicyRepository and PolicyEventBase) and the Logical Resource ABE (ReplacementSet)</font><br/><br/>