Figure PR.28 - Example Subclasses of PhysicalComponent

A PhysicalComponent is a managed entity that can reside either in an Equipment or an EquipmentHolder object, but cannot be used as a stand-alone object. From a management point-of-view, this object either cannot or does not need to be split into its constituent parts. Any piece of hardware that is not a PhysicalLink, PhysicalConnector, Equipment, or EquipmentHolder, is a subclass of this class. Some important subclasses of PhysicalComponent are shown below.<br/>The example subclasses are exemplified by the following description of the Chip class. A Chip is a concrete class that models different types of Chips that are either directly configurable by the end-user (e.g., a programmable device) and/or represent FRUs (e.g., a special ASIC that can be upgraded by replacing it with a new version of that same ASIC).<br/>