The CIM_SoftwareFeature class defines a particular function or capability of a product or application system. This class in intended to capture the level of granularity that is meaningful to a consumer or user of a product rather than the units that reflect how the product is built or packaged. The latter detailed is captured using a CIM_SoftwareElement class. When a software feature can exist on multiple platforms or operating systems (for example, a client component of a three tiered client/server applications might run on Solaris, Windows NT, and Windows 95), a software feature is a collection of all the software elements for these different platforms. In this case, the users of the model must be aware of this situation since typically they will be interested in a sub-collection of the software elements required for a particular platform. Software features are always defined in the context of a CIM_Product class using the CIM_ProductSoftwareFeatures association since features are delivered through products. Optionally, software features from one or more products can be organized into application systems using the CIM_ApplicationSystemSoftwareFeature association.
CIM_SoftwareFeature - child subclasses in ROOT\CIMV2\ms_409
'The InstallDate property is datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.'
'The Name property defines the label by which the object is known to the world outside the data processing system. This label is a human-readable name that uniquely identifies the element in the context of the element's namespace.'
'The Status property is a string indicating the current status of the object. Various operational and non-operational statuses can be defined. Operational statuses are "OK", "Degraded" and "Pred Fail". "Pred Fail" indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive. Non-operational statuses can also be specified. These are "Error", "Starting", "Stopping" and "Service". The latter, "Service", could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is on-line, yet the managed element is neither "OK" nor in one of the other states.'
' The CIM_SoftwareFeature class defines a particular function or capability of a product or application system. This class in intended to capture the level of granularity that is meaningful to a consumer or user of a product rather than the units that reflect how the product is built or packaged. The latter detailed is captured using a CIM_SoftwareElement class. When a software feature can exist on multiple platforms or operating systems (for example, a client component of a three tiered client/server applications might run on Solaris, Windows NT, and Windows 95), a software feature is a collection of all the software elements for these different platforms. In this case, the users of the model must be aware of this situation since typically they will be interested in a sub-collection of the software elements required for a particular platform. Software features are always defined in the context of a CIM_Product class using the CIM_ProductSoftwareFeatures association since features are delivered through products. Optionally, software features from one or more products can be organized into application systems using the CIM_ApplicationSystemSoftwareFeature association. '