Reflective Analysis and Design for Adapting Object Run-Time Behavior

Cazzola, Walter; Ghoneim, Ahmed; Saake, Gunter

doi:10.1007/3-540-46102-7_29

Cited by 8 publications

(6 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A reflection mechanism provides the ability of the SBA to observe and to modify its computation [3]. We introduce this mechanism in ReMoSSA for dynamically adapting the service and composing in two levels: the first level is the base level.…”

Section: Self-adaptive Mechanisms In Remossamentioning

confidence: 99%

ReMoSSA: Reference Model for Specification of Self-adaptive Service-Oriented-Architecture

Cherif¹,

Djemaa²,

Amous³

2014

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Abstract. Specification of SOA has been used to decrease the complexity of service's development to illustrate the self-adaptive applications. On the one hand, it is a means that provides us the appropriate vocabulary for describing the self-adaptive applications. On the other hand, it grants the key architectural characteristics of self-adaptive service under highly changing environments. In this paper, we present ReMoSSA a formal reference model for specifying selfadaptive Service-Based Applications (SBA). ReMoSSA integrates selfadaptation mechanisms and strategies to provide autonomic and adaptable services. It provides a dynamic monitoring and dynamic adaptation in the design phase. ReMoSSA reduces the cost and the effort of maintenance.

show abstract

Section: Self-adaptive Mechanisms In Remossamentioning

confidence: 99%

ReMoSSA: Reference Model for Specification of Self-adaptive Service-Oriented-Architecture

Cherif¹,

Djemaa²,

Amous³

2014

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

show abstract

“…In (Cazzola et al, 2002;Cazzola et al, 2004) we have proposed an infrastructure that dynamically adapts software systems using architectural reflection. The key idea of architectural reflection is to reuse the knowledge of the design phase to evolve and validate the structure and behavior of a software system at runtime.…”

Section: Architectural Reflectionmentioning

confidence: 99%

“…Our approach is based on our previous work on architectural reflection (Cazzola et al, 2002;Cazzola et al, 2004). Architectural reflection map the knowledge from the design phase, e.g.…”

Section: Introductionmentioning

confidence: 99%

Evolutionary Software Life Cycle for Self-Adapting Software Systems

Ghoneim¹,

Apel²,

Saake³

2005

Proceedings of the Seventh International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Abstract:Reactive non-stoppable software systems perform tasks continually to face environmental changes. These changes require for adapting strategies of the set of behaviors, or to add new ones according to the ability of the underlying hardware capabilities. Current approaches to runtime adaptation focus only on information which is provided by the implementation phase. Design information is not involved, even though it is extremely useful for adaptation, because they holds the semantics of the regarding software system. We present an evolutionary life cycle for self-evolving software systems by combining the traditional spiral life cycle model, known from software development with a reflective architecture which processes design information. This allows the iterative evolution of software systems at runtime. The reflective architecture (especially the metalevel) evolves the behavior and structure of the software system using its design information. Furthermore, we propose the concept of meta-feedback to react flexibly on the continuous changes of the environment. The proposed life cycle practicability is illustrated through a case study, a robot control software.

show abstract

“…In addition, classes can report the interfaces they implement. These automatic reporting mechanisms make powerful meta-programming approaches possible, such as the coordination explained here, the deployment of programs as web services, as well as incorporation of tools in many other programming contexts (Cazzola et al 2002). …”

Section: The “Introspective Observer” Coordination Design Of the Geovmentioning

confidence: 99%

The geoviz toolkit: using component-oriented coordination methods for geographic visualization and analysis

Hardisty

Robinson

2011

International Journal of Geographical Information Science

View full text Add to dashboard Cite

In this paper we present the GeoViz Toolkit, an open-source, internet-delivered program for geographic visualization and analysis that features a diverse set of software components which can be flexibly combined by users who do not have programming expertise. The design and architecture of the GeoViz Toolkit allows us to address three key research challenges in geovisualization: allowing end users to create their own geovisualization and analysis component set on-the-fly, integrating geovisualization methods with spatial analysis methods, and making geovisualization applications sharable between users. Each of these tasks necessitates a robust yet flexible approach to inter-tool coordination. The coordination strategy we developed for the GeoViz Toolkit, called Introspective Observer Coordination, leverages and combines key advances in software engineering from the last decade: automatic introspection of objects, software design patterns, and reflective invocation of methods.

show abstract

Reflective Analysis and Design for Adapting Object Run-Time Behavior

Cited by 8 publications

References 13 publications

ReMoSSA: Reference Model for Specification of Self-adaptive Service-Oriented-Architecture

ReMoSSA: Reference Model for Specification of Self-adaptive Service-Oriented-Architecture

Evolutionary Software Life Cycle for Self-Adapting Software Systems

The geoviz toolkit: using component-oriented coordination methods for geographic visualization and analysis

Contact Info

Product

Resources

About