How clausklein/ossie works
Main Components
• OSSIE Core / Framework:
• Core OSSIE framework components found in the “system/ossie” directory. This layer contains the application framework, device, and component management (such as DeviceManager_impl, DomainManager_impl, LifeCycle_impl, etc.).
• Signal Processing and DSP Modules:
• Use the “system/SigProc” directory as the DSP/signal processing layer which includes filters, modulation/demodulation, PLL, and other processing routines.
• Custom and Standard Interfaces:
• “system/customInterfaces” and “system/standardInterfaces”, which encapsulate the IDL files, interface definitions, and core common functionality (such as FM_Control, Radio_Control, and various media/port interfaces).
• Radio Components:
• In the “components” directory, many SDR algorithms and processing units are implemented (for example, AutomaticGainControl, ChannelDemo, Decimator, TxDemo, RxDemo, JPEG_VideoViewer, WebCamCapture, and others). Group these as independent, modular radio components.
• Platform-Specific Layers:
• The “platform” directory holds the abstraction for different hardware interfaces and target platforms (e.g., GPP, Sound_in, Sound_out, USRP, and associated nodes for device deployments). These modules manage direct hardware or OS interfaces.
• Tools and Waveforms:
• A section for “tools” (like WaveDev, ALF, ALF_plugins) that are used for component creation and system configuration, along with “waveforms” (OSSIE demo waveforms) that define how components are assembled into complete radio systems.
• Build and Configuration Infrastructure:
• While not the primary logical components, illustrate that the entire project relies on autotools (configure.ac, Makefile.am files, etc.) which support a flexible build system.
Component Relationships and Interactions
• Data Flow & Control:
• Interface Connectors:
• How custom and standard interfaces (IDL definitions) provide a contract between components and the OSSIE framework, enabling CORBA-based communication.
• Component Integration:
• That individual radio processing components (in the “components” directory) communicate with one another and with the platform layer, orchestrated by the OSSIE framework.
Architectural Patterns & Design Principles
• Modularity:
• Each component and module (e.g., AutomaticGainControl, Decimator, RxDemo, TxDemo) acts as an independently built and testable unit.
• Layered Architecture:
• Top-level separation between the hardware interface/platform abstraction, the DSP/signal processing functions, the OSSIE middleware, and the high-level application components.
• Use of CORBA and IDL:
• Role of CORBA in connecting components via standard and custom interfaces (derived from IDL files in standardInterfaces and customInterfaces).
• Build & Configuration Flexibility:
• Omnipresence of autotools for configuration and building, indicating how the project supports easy integration and extensibility.
Relevant Technologies and Frameworks
• C++ on Linux as the main programming language/environment.
• CORBA (omniORB) for inter-process and inter-component communication.
• Xerces-C for XML parsing, especially in generating and handling component descriptors (look at the XML files and DTDs).
• Boost and Python3 for additional support in tooling and build/configuration scripts.
• Autotools (autoconf, automake, libtool) driving the build process.