Supporting Adaptable Distributed Systems with FORMAware
ICDCSW '04 Proceedings of the 24th International Conference on Distributed Computing Systems Workshops - W7: EC (ICDCSW'04) - Volume 7
QoS Management specification support for multimedia middleware
Journal of Systems and Software
Performance modeling and analysis of software architectures: an aspect-oriented UML based approach
Science of Computer Programming - Special issue on system and software architectures(IWSSA'04)
Runtime recovery and manipulation of software architecture of component-based systems
Automated Software Engineering
Post-development software architecture
ACM SIGSOFT Software Engineering Notes
Efficient development of highly reusable distributed systems using the TCAO
ACST'07 Proceedings of the third conference on IASTED International Conference: Advances in Computer Science and Technology
FORMAware: framework of reflective components for managing architecture adaptation
SEM'02 Proceedings of the 3rd international conference on Software engineering and middleware
Hi-index | 0.00 |
Abstract: Large scale distributed systems are typically evolving environments that have to deal with interoperability, scalability, mobility and QoS adaptability requirements. Generically, these systems need adaptation mechanisms to cope with short-term (cf. programmed reconfiguration) and long-term requirements (cf. evolutionary reconfiguration). In this paper we propose a reflective component-based framework with architecture style awareness for managing architecture composition and constraining adaptation. Specifically, this framework provides the necessary tools to generate and manipulate the programming model abstractions (i.e. components, connectors and respective properties and interfaces). The framework offers a principled way to deal with both introspection and adaptation of basic and composite components. It provides the developers with the ability to choose, extend and modify architecture style managers. These managers are responsible to represent and check architecture constraints both at development and deployment time, i.e. before any architectural reconfiguration may be committed.