CORBA is a well established technology in many industry sectors such as defense, telecommunications, software defined radio, financial services, manufacturing and continues to be the most successful open standard in supporting distributed heterogeneous mission critical systems that require exceptional levels of performance and QoS.
The CORBA object model is the industry standard, cross- platform, cross-language distributed object model for mission-critical systems. The CORBA object model enables software applications to invoke operations on distributed objects without concern for object location, programming language, OS platform, communication protocols, interconnections or hardware.
The OMG adopted the CORBA Component Model (CCM) to extend the original CORBA object model to support component based applications. The CCM is included in the CORBA 3 specification and extends the CORBA 2 object model by defining features and services that enable application developers to implement, manage, configure, and deploy components that integrate commonly used CORBA services, such as transactions, security, persistent state, and event notification services, in a standard environment. CCM also allows greater software reuse for servers and provides greater flexibility for deploying and configuring CORBA applications.
Benefits of Component Based Development
Component based software development focuses on building software systems by integrating existing software components. The aim of this approach is to ensure that individual parts of software applications are written only once rather than many times. Software applications are assembled through reuse of pre-built components rather than being rewritten from scratch.
Benefits of component based software development include:
• Altering development emphasis from programming software to composing software systems
• Reduction in time to market for new applications
• Increases reuse of existing software
• Better software reuse improves software quality and reduces maintenance costs
• Provides a much cleaner separation of concerns – container programming model hides many of the underlying middleware complexities from the developer
CCM components are the basic building blocks in a CCM system. A major strength of CCM derives from standardizing the component development cycle using mature CORBA 2 products as its middleware infrastructure. Component developers using CCM to define the IDL interfaces that component implementations will support. Next, they implement components using tools supplied by CCM providers. The resulting component implementations can then be packaged into an assembly file, such as a shared library, a JAR file, or a DLL, and linked dynamically. Finally, a deployment mechanism supplied by a CCM provider is used to deploy the component in a component server that hosts component implementations by loading their assembly files. Components therefore execute in component servers and are available to process client requests.
Related Technologies
CORBA | Real-Time CORBA | CORBA/e | MinimumCORBA | CORBA IDL | CORBA COS | CORBA & DDS | Open Source CORBA
Related PrismTech OpenFusion CORBA Products
