Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary
CIM_SoftwareElementServiceImplementation --> CIM_Dependency --> [top]
Class Declaration Attributes Name Value SUPERCLASS CIM_Dependency NAME CIM_SoftwareElementServiceImplementation
Class CIM_SoftwareElementServiceImplementation Qualifiers Name Type Value From Class Version string 2.6.0 CIM_SoftwareElementServiceImplementation Description string An association between a Service and how it is implemented by one or more executable SoftwareElements. Note that this association is restricted to ’ executable ’ Elements. In earlier phases of deployment, the SoftwareFeatureService Implementation association is adequate and recommended. The relationship between this association and Software FeatureServiceImplementation is more fully described here. SoftwareElementServiceImplementation allows the description of greater granularity than SoftwareFeatureService Implementation, when a SoftwareFeature is fully deployed and results in several executable Elements. These Elements may implement several different Services. Since SoftwareFeatures decompose into SoftwareElements, it is possible to describe how software implements a Service by using either this association or the SoftwareFeature ServiceImplementation relationship. One or the other should be chosen. Both associations should not be used for a single Service instance, since their information is redundant. This relationship is especially important when the SoftwareFeature and Product aspects are not described for a SoftwareElement (ie, when the acquisition and deployment of the software is not detailed). In this case, the Software ElementServiceImplementation association is the only one available to describe how a Service is implemented in software. Since SoftwareFeatures are not instantiated, it is not possible to use the SoftwareFeatureService Implementation association. The cardinality of this association is many-to-many. A Service may be provided by more than one SoftwareElement. If this is true, it is assumed that the SoftwareElements operate in conjunction. And, any SoftwareElement may provide more than one Service. CIM_SoftwareElementServiceImplementation Association boolean true CIM_SoftwareElementServiceImplementation Association boolean true CIM_Dependency Description string CIM_Dependency is a generic association used to establish dependency relationships between ManagedElements. CIM_Dependency
Properties Name Type Value Qualifiers ClassOrigin Antecedent CIM_SoftwareElement ref Override
Description
KeyCIM_SoftwareElementServiceImplementation Dependent CIM_Service ref Override
Description
KeyCIM_SoftwareElementServiceImplementation Property Qualifiers
Property Antecedent Qualifiers Name Type Value From Class Override string Antecedent CIM_SoftwareElementServiceImplementation Description string The executable SoftwareElement implementing the Service. CIM_SoftwareElementServiceImplementation Key boolean true CIM_SoftwareElementServiceImplementation
Property Dependent Qualifiers Name Type Value From Class Override string Dependent CIM_SoftwareElementServiceImplementation Description string The Service implemented by the SoftwareElement. CIM_SoftwareElementServiceImplementation Key boolean true CIM_SoftwareElementServiceImplementation
Property Antecedent Qualifiers Name Type Value From Class Key boolean true CIM_Dependency Description string Antecedent represents the independent object in this association. CIM_Dependency
Property Dependent Qualifiers Name Type Value From Class Key boolean true CIM_Dependency Description string Dependent represents the object that is dependent on the Antecedent. CIM_Dependency
Method Qualifiers
Parameters
Parameter Qualifiers
Association
ClassReference
ClassRole CIM_DependencyContext CIM_Dependency Dependency