Aspect] is a simple and practical aspect-oriented extension to Java With just a few new constructs, AspectJ provides support for modular implementation of a range of crosscutting concerns. In AspectJ's dynamic join point model, join points are well-defined points in the execution of the program; pointcuts are collections of join points; advice are special method-like constructs that can be attached to pointcuts; and aspects are modular units of crosscutting implementation, comprising pointcuts, advice, and ordinary Java member declarations. AspectJ code is compiled into standard Java bytecode. Simple extensions to existing Java development environments make it possible to browse the crosscutting structure of aspects in the same kind of way as one browses the inheritance structure of classes. Several examples show that AspectJ is powerful, and that programs written using it are easy to understand.

An overview of AspectJ

[서평]「Component Software」 - Beyond Object-Oriented Programming -

Service Oriented Architecture Concepts Technology And Design

Assurance requirements were included in the disposal regulations to compensate in a qualitative manner for the inherent uncertainties in projecting the behavior of natural and engineered components of the WIPP for many thousands of years (50 FR 38072). Section 194.42 is one of the six assurance requirements in the Compliance Criteria. Section 194.42 specifically addresses requirements for monitoring the disposal system during preand post-closure operations. This requirement distinguishes between preand post-closure monitoring because of the differences in monitoring techniques used to access the repository during operations (pre­ closure) and after the repository has been backfilled and sealed (post-closure). The purpose of monitoring is to confirm that the repository is behaving as predicted.

https://repository.kallipos.gr/bitstream/11419/859/1/02_chapter_A1.pdf

Monitoring στη ΜΕΘ

In an environment where computing power is ubiquitous, software engineers need to cater for many different variables beyond their control. They face what has been termed the pervasive problem. Their products need to be adaptable and portable, yet still retain a simple code base. Context-Oriented Programming (COP) is a new method of programming which aims to alleviate these problems by incorporating context as a first-class construct of a programming language, much in the same way that variables, classes, and functions form the first-class constructs of many modern languages.
A context-oriented program is one with many ‘gaps’ or ‘open-terms’, and the context-filling operation completes such a program by dynamically selecting portions of code from a repository of candidates to fill these gaps. This selection process is based on the execution context of the program and a description of the open-term’s requisites.
This paper describes the requirements for COP, focusing on this fundamental operation of context-filling. An implementation which meets many of these requirements is also presented.

Context-oriented programming

A survey on engineering approaches for self-adaptive systems

The complexity of information systems is increasing in recent years, leading to increased effort for maintenance and configuration. Self-adaptive systems (SASs) address this issue. Due to new computing trends, such as pervasive computing, miniaturization of IT leads to mobile devices with the emerging need for context adaptation. Therefore, it is beneficial that devices are able to adapt context. Hence, we propose to extend the definition of SASs and include
context adaptation. This paper presents a taxonomy of self-adaptation and a survey on engineering SASs. Based on the taxonomy and the survey, we motivate a new perspective on SAS including context adaptation.

A survey on engineering approaches for self-adaptive systems (extended version)

Various trends such as mobility of devices, Cloud Computing, or Cyber-Physical Systems lead to a higher degree of distribution. These systems-of-systems need to be integrated. The integration of various subsystems still remains a challenge. Self-improvement within self-adaptive systems can help to shift integration tasks from the static design time to the runtime, which fits the dynamic needs of these systems. Thus, it can enable the integration of system parts at runtime. In this paper, we define self-improvement as an adaptation of an Autonomic Computing system's adaptation logic. We present an overview of approaches for self-improvement in the domains of Autonomic Computing and self-adaptive systems. Based on a taxonomy for self-adaptation, we compare the approaches and categorize them. The categorization shows that the approaches focus either on structural or parameter adaptation but seldomly combine both. Based on the categorization, we elaborate challenges, that need to be addressed by future approaches for offering self-improving system integration at runtime.

Comparison of Approaches for Self-Improvement in Self-Adaptive Systems

Various trends such as mobility of devices, Cloud Computing, or Cyber-Physical Systems lead to a higher degree of distribution. These systems-of-systems need to be integrated.
The integration of various subsystems still remains a challenge. Self-improvement within self-adaptive systems can help to shift
integration tasks from the static design time to the runtime, which fits the dynamic needs of these systems. Thus, it can enable the
integration of system parts at runtime.
In this paper, we define self-improvement as an adaptation of an Autonomic Computing system’s adaptation logic. We present an overview of approaches for self-improvement in the domains
of Autonomic Computing and self-adaptive systems. Based on a taxonomy for self-adaptation, we compare the approaches and categorize them. The categorization shows that the approaches
focus either on structural or parameter adaptation but seldomly combine both. Based on the categorization, we elaborate challenges, that need to be addressed by future approaches for
offering self-improving system integration at runtime.

Comparison of approaches for self-improvement in self-adaptive systems (extended version)

While Autonomic Computing can ease the maintenance of systems through adaptations [1], the development of Autonomic Computing systems itself introduces a high complexity. Literature suggests that reusable processes for the development and reusable components in the adaptation logic can reduce the complexity. Existing approaches aim to reduce this complexity with tools and frameworks for specific tasks in the development of the adaptation logic of Autonomic Computing systems. However, to the best of our knowledge, none of these approaches offer an Integrated Development Environment (IDE) for it. In this paper, we extend FESAS -- our framework for building reusable adaptation logic components -- with Eclipse plug-ins integrated into the FESAS IDE for a simplified development of MAPE components as well as a process for deployment of the components. In this paper, we present these tools. Further, we evaluate their potential to ease the development of self-adaptive systems within five example cases. Last, we discuss the benefits and limitations of the FESAS IDE.

Felix Maximilian Roth

Papers

A survey on engineering approaches for self-adaptive systems

A survey on engineering approaches for self-adaptive systems (extended version)

Comparison of Approaches for Self-Improvement in Self-Adaptive Systems

Comparison of approaches for self-improvement in self-adaptive systems (extended version)

FESAS IDE: An Integrated Development Environment for Autonomic Computing