Configuration management for distributed software services
Proceedings of the fourth international symposium on Integrated network management IV
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Reflection, self-awareness and self-healing in OpenORB
WOSS '02 Proceedings of the first workshop on Self-healing systems
An Architecture-Based Approach to Self-Adaptive Software
IEEE Intelligent Systems
An Event-Based Architecture Definition Language
IEEE Transactions on Software Engineering
ECCOP '98 Proceedings of the 12th European Conference on Object-Oriented Programming
Essentials of Constraint Programming
Essentials of Constraint Programming
Composite component support for EJB
WISICT '04 Proceedings of the winter international synposium on Information and communication technologies
The design of a configurable and reconfigurable middleware platform
Distributed Computing
Encapsulation of structural adaptation by composite components
WOSS '04 Proceedings of the 1st ACM SIGSOFT workshop on Self-managed systems
| Hi-index | 0.00 |
Components should provide maximum flexibility to increase their reusability in different applications and to work under changing environment conditions as part of a single application. Thus, adaptation and reconfiguration mechanisms of single components and component assemblies play a crucial role in achieving this goal. In this paper we present a model of Adaptable Components that allows modelling of adaptation and reconfiguration operations taking place at development, deployment or runtime. The concept of composite components is utilized to encapsulate adaptation operators and to map component parameters to different predefined internal configurations of subcomponents. The component model is not tied to a particular component platform. Instead, it can be mapped to existing component platforms like EJB using an MDA approach. Different Platform-Specific Models for the same target component platform enable tailored flexibility for particular component deployments. For example, a model can support or not support runtime reconfiguration. Extensions to UML diagrams are introduced to graphically model reconfiguration operations.