Adapting heterogeneous software components that present mismatching interaction behaviour is one of the crucial problems in Component-Based Software Engineering. The process of component adaptation can be synthesized by a transformation from an initial specification (of the requested adaptation) to a revised specification (expressing the actual adaptation that will be featured by the deployed a...

Component-based development is based on the idea of building software systems by composing preexisting components. Connectors are the ‘glue’ for composing components. Therefore, it is important to consider connectors as first-class entities and provide adequate descriptions of them to facilitate their understanding and promote their reuse. We have defined a catalogue of component connectors to ...

This paper describes an approach to component-based software engineering based on a formal description of design patterns. The architectural design information, captured by design patterns, is made explicit and represented in a declarative way, being packaged into tangible artifacts as building block design components in the development process. These design component descriptions can be instan...

Component adaptation is widely recognised to be one of the crucial problems in Component-Based Software Engineering (CBSE). We present here a formal methodology for the soft adaptation of components presenting mismatching interaction behaviours. The notions of access rights (associating components with the services they are allowed to use), and sub-servicing (providing alternative services in p...

We describe the design of an object-oriented library of software components that are suitable for constructing simulations of systems of interacting particles. The emphasis of the discussion is on the general design of the components and how they interact, and less on details of the programming interface or its implementation. Example code is provided as an aid to understanding object-oriented ...

More and more systems are developed from components instead of from scratch. Reusing components has many advantages: The development time dramatically decreases, the usability of the products increases, the production costs usually decrease, and so on. However, there is a big difference between a “classic” and component-based development, and there are many pitfalls which may lead to an unsucce...

In ongoing work, we advocate the integration of models and code as two equal constituents of software components. This approach can be followed to create flexible and self-adaptive software. We claim to extend this direction as a conceptual and technological basis for combining adaptation and evolution to achieve longevity. As a stimulus for discussions at the workshop, we present our work on m...