Class CIM_FRUIncludesSoftwareFeature

The FRUIncludesSoftwareFeature association identifies the software features packaged with a particular FRU. A common way this association can be used is to support a management task to determine if a particular FRU is compatible with a particular hardware product. In order to determine whether or not a FRU is compatible with a particular hardware product, the following conditions need to verified: (1) Is the physical package of the FRU compatible with the slots or equivalent of the hardware device? (2) Are there any physical constraints (like power consumption) that prevent the FRU from being installed properly? (3) Are the software features packaged with the FRU compatiable with the underlying operating system and other software already installed in the hardware product? This latter question can be answered by first seeing if an instance of the FRUIncludesSoftwareFeature association exists. If it does, then the compatibility of each SoftwareFeature can be determined by evaluating the Check classes that are referenced by the SoftwareElementChecks association on each SoftwareElement. For example, there might be a SoftwareElementVersionCheck that declares that a SoftwareElement of the FRU's SoftwareFeature is not compatible with another SoftwareFeature.

Class Hierarchy

CIM_FRUIncludesSoftwareFeature

Direct Known Subclasses

None.

Class Qualifiers

NameData TypeValueScopeFlavors
AggregationbooleantrueNone OVERRIDABLE= false
AssociationbooleantrueNone OVERRIDABLE= false
DescriptionstringThe FRUIncludesSoftwareFeature association identifies the software features packaged with a particular FRU. A common way this association can be used is to support a management task to determine if a particular FRU is compatible with a particular hardware product. In order to determine whether or not a FRU is compatible with a particular hardware product, the following conditions need to verified: (1) Is the physical package of the FRU compatible with the slots or equivalent of the hardware device? (2) Are there any physical constraints (like power consumption) that prevent the FRU from being installed properly? (3) Are the software features packaged with the FRU compatiable with the underlying operating system and other software already installed in the hardware product? This latter question can be answered by first seeing if an instance of the FRUIncludesSoftwareFeature association exists. If it does, then the compatibility of each SoftwareFeature can be determined by evaluating the Check classes that are referenced by the SoftwareElementChecks association on each SoftwareElement. For example, there might be a SoftwareElementVersionCheck that declares that a SoftwareElement of the FRU's SoftwareFeature is not compatible with another SoftwareFeature.None TRANSLATABLE= true

Association References

NameClass OriginReference Class
ComponentCIM_FRUIncludesSoftwareFeatureCIM_SoftwareFeature
FRUCIM_FRUIncludesSoftwareFeatureCIM_FRU