2010
DOI: 10.1007/s10270-010-0162-z
View full text |Buy / Rent full text
|
Sign up to set email alerts
|

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 … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 8 publications
(15 citation statements)
references
References 52 publications
(66 reference statements)
0
15
0
Order By: Relevance
“…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.…”
Section: Action Specificationmentioning
confidence: 99%
See 1 more Smart Citation
“…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.…”
Section: Action Specificationmentioning
confidence: 99%
“…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.…”
Section: Introductionmentioning
confidence: 99%
“…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).…”
Section: Architecture Adaptabilitymentioning
confidence: 99%
“…(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.…”
Section: Architecture Adaptabilitymentioning
confidence: 99%
“…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.…”
Section: Introductionmentioning
confidence: 99%