Self organising software architectures
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Acme: architectural description of component-based systems
Foundations of component-based systems
Exploiting architectural design knowledge to support self-repairing systems
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Self-organising software architectures for distributed systems
WOSS '02 Proceedings of the first workshop on Self-healing systems
A Framework for Constraint-Based Deployment and Autonomic Management of Distributed Applications
ICAC '04 Proceedings of the First International Conference on Autonomic Computing
Preserving Architectural Choices throughout the Component-based Software Development Process
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Simplifying transformation of software architecture constraints
Proceedings of the 2006 ACM symposium on Applied computing
Constraint-Based deployment of distributed components in a dynamic network
ARCS'06 Proceedings of the 19th international conference on Architecture of Computing Systems
| Hi-index | 0.00 |
Software architectures are often designed with respect to some architecture patterns, like the pipeline and peer-to-peer. These patterns are the guarantee of some quality attributes, like maintainability or performance. These patterns should be dynamically enforced in the running system to benefit from their associated quality characteristics at runtime. In dynamic hosting platforms where machines can enter the network, offering new resources, or fail, making the components they host unavailable, these patterns can be affected. In addition, in this kind of infrastructures, some resource requirements can also be altered. In this paper we present an approach which aims at dynamically assist deployment process with information about architectural patterns and resource constraints. This ensures that, faced with disconnections or machine failures, the runtime system complies permanently with the original architectural pattern and the initial resource requirements.