A Framework for Rule-Based Dynamic Adaptation

Modeling adaptation with Klaim

“…[31], or the policy-based one, see e.g. [29]) and, at the same time, to provide a formal proof of relative expressiveness of the primitives suggested by the considered approaches.…”

A White Box Perspective on Behavioural Adaptation

“…(ii) It allows us to relate approaches presented independently and in different areas but sharing, essentially, the same category of control data. This is, e.g., the case of the approaches based on modes of operation proposed by the Software Engineering [11] adaptation coordination strategies adaptation strategy 4.1 [48] adaptation rules adaptation strategy 5.3 [15] architecture architecture 3.1 [46] architecture architecture 3.2 [60] architecture architecture 3.2 [66] module stack architecture 3.2 [22] current workflow architecture 3.2 [7] connectors architecture 3.2 [11] architecture architecture 4.1 [76] effector channel architecture 4.3 [48] set of activities architecture 5.3 [61] entire programs entire program 4.1 [55] rewrite rules entire program 4.2 [35] processes entire program 4.3 [30] processes entire program 4.3 [28] features operation mode 4.1 [53] regions operation mode 4.1 [83] operation mode operation mode 4.1 [1] active configuration operation mode 4.1 [72] active configuration operation mode 4.1 [19] control proposition operation mode 4.1 [82] steady state programs operation mode 4.1 [42] state space zones operation mode 4.1 [33] graph rewrite rules operation mode 4.2 [80] base level Petri net operation mode 4.3 [51] adaptor processes operation mode 4.3 [16] adaptable (local) processes operation mode 4.3 [69] context stack operation mode 5.1 [36] advices operation mode 5.2 [44] policies operation mode 5.3 community with paradigm-oriented approaches and by the Theoretical Computer Science community with automata and process-algebraic approaches. (iii) It allows us to compare approaches apparently similar (and falling in the same section) but based on different categories of control data.…”

“…The construction can be iterated, as the manager itself can be an adaptable component. Concrete instances of this scenario can be found, among others, in [11,48,23]. For example, in the latter, components follow plans to perform their tasks and re-planning is used to overcome unpredicted situations that may make current plans inefficient or impossible to realize.…”

“…The key idea to achieve adaptation along the lines of the MAPE-K framework is for the manager to control the context stack and for the managed component to access it in a read-only manner. The points of the code in which the managed component queries the current context stack are called activation hooks (adaptation hooks in [48] and in [35], as we shall see in Sections 5.2 and 5.3, respectively).…”

“…The authors of [48] propose a framework for dynamic adaptation based on the combination of adaptation hooks, which specify where to apply adaptation, and policies called adaptation rules, which specify when and how to apply it. In their approach an adaptable application is an application that exposes part of its states and the set of activities that it performs in a suitable interface called application interface.…”