CIM211 Class Declaration
CIM_SoftwareElementSAPImplementation

Table of Contents:
Class Hierarchy
Class Attributes
Class Qualifiers
Properties
Methods
Associations in which the class can participate
Sub Profiling Summary

Class Hierarchy

CIM_SoftwareElementSAPImplementation --> CIM_Dependency --> [top]

Class Attributes

Class Declaration Attributes
NameValue
SUPERCLASSCIM_Dependency
NAMECIM_SoftwareElementSAPImplementation

Class Qualifiers

Class CIM_SoftwareElementSAPImplementation Qualifiers
NameTypeValueFrom Class
Versionstring2.6.0 CIM_SoftwareElementSAPImplementation
DescriptionstringAn 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
Associationbooleantrue CIM_SoftwareElementSAPImplementation
Associationbooleantrue CIM_Dependency
DescriptionstringCIM_Dependency is a generic association used to establish dependency relationships between ManagedElements. CIM_Dependency

Properties

Properties
NameTypeValueQualifiersClassOrigin
AntecedentCIM_SoftwareElement ref Override
Description
Key
CIM_SoftwareElementSAPImplementation
DependentCIM_ServiceAccessPoint ref Override
Description
Key
CIM_SoftwareElementSAPImplementation

Property Qualifiers

Property Antecedent Qualifiers
NameTypeValueFrom Class
OverridestringAntecedent CIM_SoftwareElementSAPImplementation
DescriptionstringThe executable SoftwareElement implementing the SAP. CIM_SoftwareElementSAPImplementation
Keybooleantrue CIM_SoftwareElementSAPImplementation

Property Dependent Qualifiers
NameTypeValueFrom Class
OverridestringDependent CIM_SoftwareElementSAPImplementation
DescriptionstringThe ServiceAccessPoint implemented by the SoftwareElement. CIM_SoftwareElementSAPImplementation
Keybooleantrue CIM_SoftwareElementSAPImplementation

Property Antecedent Qualifiers
NameTypeValueFrom Class
Keybooleantrue CIM_Dependency
DescriptionstringAntecedent represents the independent object in this association. CIM_Dependency

Property Dependent Qualifiers
NameTypeValueFrom Class
Keybooleantrue CIM_Dependency
DescriptionstringDependent represents the object that is dependent on the Antecedent. CIM_Dependency

Methods

Method Qualifiers

Parameters

Parameter Qualifiers

Associations this class can participate in

Association
Class
Reference
Class
Role
CIM_DependencyContextCIM_DependencyDependency