Modeling and enforcing invariants of dynamic software architectures

Abstract

In this paper, we propose an "end-to-end" approach that supports dynamic reconfiguration of software architectures taking advantage of graphical modeling, formal methods and aspect-oriented programming. There are three ingredients of the proposal. The specification end of the solution is covered by a new UML profile enabling to specify the desired architectural style (model), its invariants and the intended reconfiguration operations. In order to verify the consistency of the model and the preservation of the invariants after every reconfiguration, we automatically generate formal specifications in Z notation from the defined model. At the runtime enforcing end of the solution, we propose to encode the enforcement logic as aspect in the AspectJ language. The third important ingredient that makes our approach end-toend is the automatic translation of formal specifications into aspect-based enforcement code.

MeidyaCoM‐policy: Approach for modelling and checking repair policies for self‐healing systems

“…Actions are reconfiguration operations. The transformation of an Action is performed using seven basic rules to automatically generate Z operation schema [1]. We do not -PseudoToSolution connects a PseudoState to a Solution.…”

“…MeidyaCoM-Policy is an extension of the MeidyaCoM project [1,2]. This project supports the modelling of correct by design publish/subscribe architectural style and the definition of the basic reconfiguration operations.…”

A UML-based Approach for Multi-scale Software Architectures

“…Each transformation corresponds to a possible refinement/abstraction. (Kallel et al, 2012) proposed a UML profile to describe software architectures. Thus, we propose to adopt the notation proposed by (Kallel et al, 2012).…”

“…(Kallel et al, 2012) proposed a UML profile to describe software architectures. Thus, we propose to adopt the notation proposed by (Kallel et al, 2012). The model is composed of five sections: The name of the operation to perform, « Require&Delete » (the part of the system to remove during the operation), « Insert » (the part of the system to create during the operation), « Re-quire&Preserve » (the part not changed during the operation),and the pre-conditions that must be verified so that the operation can be performed.…”

Adaptive security for Cloud data warehouse as a service

“…In addition, we propose to model the security requirements based on Aspect-oriented modeling [2], then map them to system entities at design time. The design is elaborated in two stages: First, the developer develops a DW Description Model (DWDM) to capture the DW functional architecture, and a CDW Security Specification Models (DWSSM) to capture security risks, requirements, and mechanisms to secure the CDW.…”