Interoperability in Component Based Software Development

The ability of information systems to operate in conjunction with each other encompassing communication protocols, hardware, software, application, and data compatibility layers. There has been considerable work in industry on the development of component interoperability models, such as CORBA, (D)COM and JavaBeans. These models are intended to reduce the complexity of software development and to facilitate reuse of off-the-shelf components. The focus of these models is syntactic interface specification, component packaging, inter-component communications, and bindings to a runtime environment. What these models lack is a consideration of architectural concerns – specifying systems of communicating components, explicitly representing loci of component interaction, and exploiting architectural styles that provide well-understood global design solutions. The development of complex business applications is now focused on an assembly of components available on a local area network or on the net. These components must be localized and identified in terms of available services and communication protocol before any request. The first part of the article introduces the base concepts of components and middleware while the following sections describe the different up-todate models of communication and interaction and the last section shows how different models can communicate among themselves.

• M. Madiajagan
• B. Vijayakumar

• Interoperability
• component packaging
• communication technology
• heterogeneous platform
• component interface
• middleware.

[1] Gray T. Leavens and Murali Sitaraman, Foundations of Component-
Based Systems, Cambridge University Press, 2000.
[2] Hofmeister, C., Nord, R. and Soni, D, Applied Software
Architecture, Addison- Wesley Longman, 2000.
[3] Serain D. Enterprise Application Integration - L- architecture
des solutions e-business, avril 2001.
[4] Fay, S. Standards and reuse. The Rational Edge, May 2003..
[5] Sessions. R. Objects and Components, ObjectWatch newsletter
number 28, June 2000.
[6] Beland, J. P. and Pos, M. Open Software Architecture Beland, J. P. and
Pos, M. Open Software Architecture.
[7] Wassermann A. I. Tools Integration in Software Engineering
Environments, spinger-verlag, Berlin, 1998, pp.138-150.
[8] Brown A. W., Component -Based Software Engineering: selected
papers from the Software Engineering Institute, Wesley - IEEE
Computer Society Press.
[9] Chan, R. Adopting RUP in a COTs implementation Project. The
Rational Edge, May 2003.
[10] Boehm B. Spiral Development: Experiences Principles, and
Refinements. Spiral Development Workshop, Ed. Wilfred J. Hansen,
February 2000.
[11] XMLFAQ(2004). The XML FAQ
http://www.ucc.ie:8080/cocoon/xmlfaq.
[12] Peltzer D. (2003) .Net & J2EE Interoperability, November 2003.
[13] Browning, D. Integrate .NET Remoting into the Enterprise Windows
Server System
http://www.ftponline.com/wss/2002_11/magazine/features.
[14] Holloway, R. Compare >NET Remoting to Web Services, Visual Studio
Magazine, Web services in the Enterprise, 12-11, 2002.
[15] TMC. The Petstore Revisited: J2EE Vs .Net Application Server
Performance Benchmark, November 2002.
[16] Object Web Consortium 2004. www.objectweb.org.
[17] Bloomberg, J. Web Services: A New Paradigm for Distributed
Computing, The Rational Edge September 2001.
[18] Linthium, D. S. Next Generation Application Integration from simple
Information to Web Service, September 2003, Addison Wesley.
[19] Newcomer, E. Decide between J2EE and .NET Web Services, Windows
Server System Magazine - 2,9, 2002.
[20] Andrews, W. Predicts 2004, Gartner-s Prediction .
http://w3.gartner.com/research/ spotlight/ assert_55117_895.jsp