Dynamic Protocol Aggregation and Adaptation for Service-Oriented Computing

Abstract

Abstract

Towards Dynamic Matching of Business-Level Protocols in Adaptive Service Compositions

“…More than just a binding, it stores the interaction constraints and provides a mechanism to intercept the messages exchanged between two roles during run-time in order to verify the interaction. The monitoring ability of ROAD contracts is discussed elsewhere [9]. Of particular relevance to the discussion in this paper, is the ability of ROAD contracts to define protocol clauses that describe permissible sequences of transactions that can occur between roles.…”

“…Our approach also provides an automatic consistency checking to ensure no violation has occurred during the changes. The reader is referred to [9] where we describe how IRS constraints can be incrementally added or deleted from ROAD contracts. …”

“…These constraints are converted into finite state automata (FSA) within the contract so that interaction can be checked at runtime, as discussed in [5,9]. (For multiple contracts in a composite, the organiser also maintains a model of any dependency constraints between these contract protocols.)…”

The Four Major Challenges of Engineering Adaptive Software Architectures

“…Contract terms define the mutual obligations of the participant roles in an organisational context. They define the interactions that are permissible or required by the participant roles, and can be used to enforce sequences of interactions [15]. Contracts can also set any non-functional requirements (NFRs), in the form of utility objects, on their roles' interactions, and monitor those interactions for compliance to those requirements.…”