Multi-view description of software architectures
ISAW '98 Proceedings of the third international workshop on Software architecture
Defining Open Software Architectures for Customized Remote Execution of Web Agents
Autonomous Agents and Multi-Agent Systems
COORDINATION '00 Proceedings of the 4th International Conference on Coordination Languages and Models
Component-Based Programming of Distributed Applications
Advances in Distributed Systems, Advanced Distributed Computing: From Algorithms to Systems
Higher-order architectural connectors
ACM Transactions on Software Engineering and Methodology (TOSEM)
Defining and modelling service-based coordinated systems
ODBASE'06/OTM'06 Proceedings of the 2006 Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, DOA, GADA, and ODBASE - Volume Part I
Towards a secure service coordination
EDBT'06 Proceedings of the 2006 international conference on Current Trends in Database Technology
| Hi-index | 0.00 |
A number of existing Distributed Processing Environments (DPEs) are eligible to serve as a coordination architecture. In order to ease the construction of distributed applications while exploiting existing DPEs, the developer should be provided with notations that allow him to characterize the coordination architecture that is the best suited to his application. Existing DPEs can be distinguished according to at least two criteria: i) the coordination protocols (e.g. RpPC, pipe-filter, tuple space) they support, and ii) the non-functional execution properties (e.g. availability, security, responsiveness) they provide. This leads us to propose a twofold formal description of coordination architectures that characterizes the coordination protocols and non-functional execution properties that are expected from the underlying DPE, hence allowing to reason about the adequacy of a DPE for supporting a given coordination architecture.