Improve component-based programs with connectors

Abstract

Interfaces rather than components carry component-based software architectures. This follows directly from the design of component interfaces and contractual obligations before the implementation of components. We suggest separating component interfaces and component services such as protocol checking, synchronization, parallelization and caching into dedicated components which we call connectors. Connectors channel the communication so that components do not communicate directly with each other. Thus connectors foster the standardization of identifiable component contracts, accelerate the development of complementing or competing components, and improve the testability, portability and maintainability of component-based programs. © Springer-Verlag Berlin Heidelberg 2006.