Several proposals for component-based development\ud methods have started to appear. However, the emphasis is\ud still very much on the development of components as\ud opposed to the development with components. The main\ud focus is on how to generate ideal reusable components not\ud on how to plug existing components and specify their\ud interactions and connections.\ud The concept of a coordination contract (Andrade and\ud Fiadeiro 1999; Andrade and Fiadeiro 2001; Andrade,\ud Fiadeiro et al. 2001) has been proposed to specify a\ud mechanism of interaction between objects based on the\ud separation between structure, what is stable, and\ud interaction, what is changeable. This separation supports\ud better any change of requirements, as contracts can be\ud replaced, added or removed dynamically, i.e. in run-time,\ud without having to interfere with the components that they\ud coordinate. A coordination contract corresponds to an\ud expressive architectural connector that can be used to plug\ud existing components.\ud In this paper we integrate the concept of a coordination\ud contract with component-based development and show\ud how coordination contracts can be used to specify the\ud connectors between components
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.