uction. in whichever way seems best for that particular Resource. PropertySet LifeCycle TestableObject PortSupplier Resource Figure 2.4a-6 Resource class parent structure. The resource inherits a specialized framework functionality. The software defined radio as a platform for cognitive radio CHAPTER 2.4a waveform control, and system control. The following The Port class is the entry point and, if desired, the sections describe each of these pieces in more detail. exit point of any component. As such, the only Hardware control function calls that are explicitly listed in the Port defi- nition are connectPort() and disconnectPort(). All other As discussed in Section 2.4a.1, a radio generally com- implementation-specific member functions are the prises a variety of different pieces of hardware. As such, actual connections, which, in the most general sense, are the framework must include the infrastructure necessary guided by the waveform's API. A component can have as to support the variety of hardware that may be used. many Ports as it requires. The implementation of the From a software placement point of view, not all hard- Port and the structure that is used to transfer information ware associated with a radio can run software. Thus, the classes that are described to handle hardware can run on between the Resource (or the Resource's child) to the Port and back is not described in the specifications and is the target hardware itself, or it can run in a proxy fashion, left up to the developer's discretion. Section 2.4a.3.1 as seen in Figure 2.4a-7. When used as a proxy, the describes the development process and describes a few hardware control software allows associated specialized patterns that can be used to create specific components. hardware to function as if it were any other type of hardware. The needs of the hardware controller in the SCA are Framework control similar to the needs of components supporting a wave- The base component classes are the basic building form. Furthermore, the component model close