Communication Patterns as Key Towards Component Interoperability

A component based software engineering approach does not per se ensure that independently developed components finally fit together. The reason is that general purpose component based approaches still provide far too much freedom with respect to defining and implementing component interfaces. There is always a gap from a general purpose software component approach towards reusable and easily composable components in a specific application domain.

[1]  Christian Schlegel,et al.  Communication Patterns as Key towards Component-Based Robotics , 2006 .

[2]  David R. Musser,et al.  STL tutorial and reference guide, second edition: C++ programming with the standard template library , 2001 .

[3]  Douglas C. Schmidt,et al.  Evaluating policies and mechanisms for supporting embedded, real-time applications with CORBA 3.0 , 2000, Proceedings Sixth IEEE Real-Time Technology and Applications Symposium. RTAS 2000.

[4]  Peter Sommerlad,et al.  Pattern-Oriented Software Architecture , 1996 .

[5]  Christian Schlegel,et al.  The software framework SMARTSOFT for implementing sensorimotor systems , 1999, Proceedings 1999 IEEE/RSJ International Conference on Intelligent Robots and Systems. Human and Environment Friendly Robots with High Intelligence and Emotional Quotients (Cat. No.99CH36289).

[6]  Steve Vinoski,et al.  Advanced CORBA® Programming with C++ , 1999 .

[7]  Douglas C. Schmidt,et al.  The Design and Performance of a Scalable ORB Architecture for CORBA Asynchronous Messaging , 2000, Middleware.