Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary
CIM_SoftwareElementSAPImplementation --> CIM_Dependency --> [top]
Class Declaration Attributes Name Value SUPERCLASS CIM_Dependency NAME CIM_SoftwareElementSAPImplementation
Class CIM_SoftwareElementSAPImplementation Qualifiers Name Type Value From Class Version string 2.6.0 CIM_SoftwareElementSAPImplementation Description string An association between a ServiceAccessPoint 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 Software FeatureSAPImplementation association is adequate and recommended. The relationship between this association and Software FeatureSAPImplementation is more fully described here. SoftwareElementSAPImplementation allows the description of greater granularity than SoftwareFeatureSAPImplementation, when a SoftwareFeature is fully deployed and results in several executable Elements. These Elements may implement several different ServiceAccessPoints. Since SoftwareFeatures decompose into SoftwareElements, it is possible to describe how software implements a SAP by using either this association or the SoftwareFeatureSAP Implementation relationship. One or the other should be chosen. Both associations should not be used for a particular AccessPoint, 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 ElementSAPImplementation association is the only one available to describe how an AccessPoint is implemented in software. Since SoftwareFeatures are not instantiated, it is not possible to use the SoftwareFeatureSAP Implementation association. The cardinality of this association is many-to-many. A ServiceAccessPoint may be provided by more than one Software Element. (If this is true, it is assumed that the Software Elements operate in conjunction.) And, any SoftwareElement may provide more than one SAP. CIM_SoftwareElementSAPImplementation Association boolean true CIM_SoftwareElementSAPImplementation 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_SoftwareElementSAPImplementation Dependent CIM_ServiceAccessPoint ref Override
Description
KeyCIM_SoftwareElementSAPImplementation Property Qualifiers
Property Antecedent Qualifiers Name Type Value From Class Override string Antecedent CIM_SoftwareElementSAPImplementation Description string The executable SoftwareElement implementing the SAP. CIM_SoftwareElementSAPImplementation Key boolean true CIM_SoftwareElementSAPImplementation
Property Dependent Qualifiers Name Type Value From Class Override string Dependent CIM_SoftwareElementSAPImplementation Description string The ServiceAccessPoint implemented by the SoftwareElement. CIM_SoftwareElementSAPImplementation Key boolean true CIM_SoftwareElementSAPImplementation
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