Managing Trade-Offs in Adaptable Software Architectures 2017
DOI: 10.1016/b978-0-12-802855-1.00014-9
|View full text |Cite
|
Sign up to set email alerts
|

Identifying and Handling Uncertainties in the Feedback Control Loop

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
1

Relationship

1
4

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 30 publications
0
3
0
Order By: Relevance
“…For presentation purposes, it was natural to follow the MAPE-K feedback control loop for identifying the technical challenges, however, questions may be asked about the appropriateness of MAPE-K loop when finding solutions to the wide range of identified challenges. Authorisation infrastructure are inherently quite complex infrastructures, which can be geographically distributed, and this might require architectural solutions for the controller that might go beyond what the classical MAPE-K loop can offer [23,74]. For example, if perpetual evaluations [73] are needed in order to obtained assurances of the confidentiality, integrity, and availability of computer based resources regarding the adaptations performed to the authorisation infrastructure, then new ways of enforcing separation of concerns are needed at the controller level.…”
Section: Discussionmentioning
confidence: 99%
“…For presentation purposes, it was natural to follow the MAPE-K feedback control loop for identifying the technical challenges, however, questions may be asked about the appropriateness of MAPE-K loop when finding solutions to the wide range of identified challenges. Authorisation infrastructure are inherently quite complex infrastructures, which can be geographically distributed, and this might require architectural solutions for the controller that might go beyond what the classical MAPE-K loop can offer [23,74]. For example, if perpetual evaluations [73] are needed in order to obtained assurances of the confidentiality, integrity, and availability of computer based resources regarding the adaptations performed to the authorisation infrastructure, then new ways of enforcing separation of concerns are needed at the controller level.…”
Section: Discussionmentioning
confidence: 99%
“…Some of the existing generic controllers, like Rainbow [3], have been effective in controlling some of aspects of software systems, which can either be structural or parametric. However, if the evolutionary software lifecycle is mapped into the four stages of the MAPE-K loop, new activities need to be associated with each of the stages [2]. For example, the analysis stage may include model checking or testing architectural configurations, These specific activities that go beyond the control of the target system, may need themselves to be self-adaptive.…”
Section: (Not So) Inspirational Mape-k Loopmentioning
confidence: 99%
“…These micro-controllers would not be restricted to the implementation of services provided by the distinct stages of a MAPE-K loop [29]. Instead, the micro-controllers would be associated with specific services that make up the individual stages of a controller [12]. For example, for the Analysis stage of the MAPE-K loop, a micro-controller would implement the services associated with integration testing [38], or model checking [36].…”
Section: A Micro-controllersmentioning
confidence: 99%