Coordination languages and their significance
Communications of the ACM
Software architecture in practice
Software architecture in practice
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
A graph based architectural (Re)configuration language
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Support for business-driven evolution with coordination technologies
IWPSE '01 Proceedings of the 4th International Workshop on Principles of Software Evolution
Managing Evolution in Telecommunication Systems
Proceedings of the IFIP TC6 / WG6.1 Third International Working Conference on New Developments in Distributed Applications and Interoperable Systems
Coordination: The Evolutionary Dimension
TOOLS '01 Proceedings of the Technology of Object-Oriented Languages and Systems
Tool Support for Coordination-Based Software Evolution
TOOLS '01 Proceedings of the Technology of Object-Oriented Languages and Systems
Enforcing Business Policies Through Automated Reconfiguration
Proceedings of the 16th IEEE international conference on Automated software engineering
Interconnecting objects via contracts
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Architectural reconfiguration using coordinated atomic actions
Proceedings of the 2006 international workshop on Self-adaptation and self-managing systems
| Hi-index | 0.00 |
A four-layer architecture is outlined for the design of systems required to accommodate higher levels of evolution and personalization. This architecture is based on the separation of four different aspects that concern change: the computations the system has to perform to ensure basic functionalities, the interactions that can be superposed among those computations to make global properties emerge, the configurations of computations and interactions that respond to current business requirements, and the "contexts" in which the system is used according to organizational policies..