2008
DOI: 10.1007/s11432-008-0052-y
|View full text |Cite
|
Sign up to set email alerts
|

A software architecture centric self-adaptation approach for Internetware

Abstract: Being one of the basic features of Internetware, self-adaptation means that the software system can monitor its runtime state and behavior and adjust them when necessary according to pre-defined policies. Focusing on the three fundamental issues of self-adaptation, including the scope, operability and trustworthiness, a software architecture (SA) centric approach for Internetware's self-adaptation is presented in this paper. All of the self-adaptive actions, i.e. monitoring, analyzing, planning and executing, … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0
2

Year Published

2009
2009
2016
2016

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 28 publications
(15 citation statements)
references
References 13 publications
0
13
0
2
Order By: Relevance
“…The original middleware mainly enables connection and interoperation between networked applications, in order to improve the portability. With the rapid growth of the Internet, the middleware has covered much broader contents and been more widely adopted [11]. First of all, different types of middleware, e.g., database access middleware, remote procedure call middleware, message middleware and distributed computing middleware, become integrated and form a new "synergy middleware".…”
Section: Evolution Of Software Runtime Platformmentioning
confidence: 99%
“…The original middleware mainly enables connection and interoperation between networked applications, in order to improve the portability. With the rapid growth of the Internet, the middleware has covered much broader contents and been more widely adopted [11]. First of all, different types of middleware, e.g., database access middleware, remote procedure call middleware, message middleware and distributed computing middleware, become integrated and form a new "synergy middleware".…”
Section: Evolution Of Software Runtime Platformmentioning
confidence: 99%
“…In order to check if this design evolution can be actually reflected to the running system, we define the following query in WildCAT: V. RELATED WORK As stated in the introduction, our approach is based on models@runtime techniques such as Rainbow [2], ABCTool [3], Plastik [4] which aims at ensuring the synchronization between a running system and its related design models. Rainbow and Plastik focus on the development of SAS by ensuring that selfadaptation does not conflict with static constraints developed at design-time.…”
Section: B Design Evolution Of the Flood Prediction Systemmentioning
confidence: 99%
“…Recent research efforts on Model-Driven Engineering (MDE) such as Rainbow [2], ABCTool [3], Plastik [4] or DiVA [5] tackle the design evolution issue by building a causal connection between abstract design models and the running system. Thus, the designer can refine and update the conceptual models and then automatically synchronize them with the running system, thus preventing developers to write by hand ad-hoc and platformdependent scripts [6].…”
Section: Introductionmentioning
confidence: 99%
“…Hong Mei et al [2] present a software architecture (SA) centric approach for Internetware's self-adaptation, focusing on the three fundamental issues of self-adaptation including the scope, operability and trustworthiness. Internetware is capable of perceiving the dynamic changes of its environment and adjust itself to meet its functionality, performance, dependability, etc.…”
Section: Related Workmentioning
confidence: 99%
“…Being one of the basic features of Internetware, self-adaptation means that the software system can monitor its runtime state and behavior and adjust them when necessary according to pre-defined policies [2]. Selfadaptive systems can configure and reconfigure themselves at run time to handle such things as changing user needs, system intrusions or faults, a changing operational environment, and resource variability [3].…”
Section: Introductionmentioning
confidence: 99%