Abstract. The goal of this roadmap paper is to summarize the state-ofthe-art and to identify critical challenges for the systematic software engineering of self-adaptive systems. The paper is partitioned into four parts, one for each of the identified essential views of self-adaptation: modelling dimensions, requirements, engineering, and assurances. For each view, we present the state-of-the-art and the challenges that our community must address. This roadmap paper is a result of the Dagstuhl Seminar 08031 on "Software Engineering for Self-Adaptive Systems, " which took place in January 2008.

Abstract. The goal of this roadmap paper is to summarize the stateof-the-art and identify research challenges when developing, deploying and managing self-adaptive software systems. Instead of dealing with a wide range of topics associated with the field, we focus on four essential topics of self-adaptation: design space for self-adaptive solutions, software engineering processes for self-adaptive systems, from centralized to decentralized control, and practical run-time verification & validation for self-adaptive systems. For each topic, we present an overview, suggest future directions, and focus on selected challenges. This paper complements and extends a previous roadmap on software engineering for self-adaptive systems published in 2009 covering a different set of topics, and reflecting in part on the previous paper. This roadmap is one of the many results of the Dagstuhl Seminar 10431 on Software Engineering for Self-Adaptive Systems, which took place in October 2010.

Abstract. It is commonly agreed that a self-adaptive software system is one that can modify itself at run-time due to changes in the system, its requirements, or the environment in which it is deployed. A cursory review of the software engineering literature attests to the wide spectrum of software systems that are described as self-adaptive. The way self-adaptation is conceived depends on various aspects, such as the users' requirements, the particular properties of a system, and the characteristics of the environment. In this paper, we propose a classification of modeling dimensions for self-adaptive software systems. Each modeling dimension describes a particular facet of the system that is relevant to self-adaptation. The modeling dimensions provide the engineers with a common set of vocabulary for specifying the self-adaptive properties under consideration and select suitable solutions. We illustrate how the modeling dimensions apply to several application scenarios.

In this paper, we discuss how for self-adaptive systems some activities that traditionally occur at development-time are moved to runtime. Responsibilities for these activities shift from software engineers to the system itself, causing the traditional boundary between developmenttime and run-time to blur. As a consequence, we argue how the traditional software engineering process needs to be reconceptualized to distinguish both development-time and run-time activities, and to support designers in taking decisions on how to properly engineer such systems.Furthermore, we identify a number of challenges related to this required reconceptualization, and we propose initial ideas based on process modeling. We use the Software and Systems Process Engineering Meta-Model (SPEM) to specify which activities are meant to be performed off-line and on-line, and also the dependencies between them. The proposed models should capture information about the costs and benefits of shifting activities to run-time, since such models should support software engineers in their decisions when they are engineering self-adaptive systems.

The important concern for modern software systems is to become more cost-effective, while being versatile, flexible, resilient, dependable, energy-efficient, customisable, configurable and self-optimising when reacting to run-time changes that may occur within the system itself, its environment or requirements. One of the most promising approaches to achieving such properties is to equip software systems with self-managing capabilities using self-adaptation mechanisms. Despite recent advances in this area, one key aspect of self-adaptive systems that remains to be tackled in depth is the provision of assurances, i.e., the collection, analysis and synthesis of evidence that the system satisfies its stated functional and non-functional requirements during its operation in the presence of self-adaptation. The provision of assurances for selfadaptive systems is challenging since run-time changes introduce a high degree of uncertainty. This paper on research challenges complements previous roadmap papers on software engineering for self-adaptive systems covering a different set of topics, which are related to assurances, namely, perpetual assurances, composition and decomposition of assurances, and assurances obtained from control theory. This research challenges paper is one of the many results of the Dagstuhl Seminar 13511 on Software Engineering for Self-Adaptive Systems: Assurances which took place in December 2013.

Self-adaptability

No abstract

Exception handling is a structuring technique that facilitates the design of software systems by encapsulating the process of error recovery. In this paper, we present a systematic approach for incorporating exceptional behaviour in the development of component-based software. The premise of our approach is that components alone do not provide the appropriate means to deal with exceptional behaviour in an effective manner, hence the need to consider the notion of collaborations for capturing the interactive behaviour between components when error recovery involves more than one component. The feasibility of the approach is demonstrated in terms of the mining control system case study.combination of exceptions that might be raised from the different components. Moreover, if the description of exceptional behaviour is not considered in a structured way, this will unavoidably increase the complexity of the system, making its understanding more difficult and thus leading to the construction of an untrustworthy system. Hence, it is necessary to incorporate exceptional behaviour in a carefully structured and controlled way that minimizes its impact on the system complexity. One solution to this problem is to adopt a systematic approach for incorporating exceptional behaviour in the development of component-based systems.Dealing with concurrent manifestations of several faults at different phases of system development has been recognized as a serious problem that has not received enough attention [1]. In the context of component-based software development, related work has been scarce and most of it associates exception handling with objects, making no attempt to consider exception handling within the software lifecycle. Although exception handling and object-oriented languages raise some conflicts, these conflicts exist mainly during the late phases of the software development [2], and some of these can be solved if exception handling is considered from the early phases of software development. In a recent work, the integration of exceptional behaviour within the software lifecycle was supported by a cooperative object-oriented approach that allows the representation of collaborative behaviour between objects at different phases of the software development [3]. The approach presented in this paper is distinct from the co-operative object-oriented approach in several aspects. The most significant aspect is the fact that our approach is considered in the context of an existing methodology, which allows us to describe the incorporation of exception handling in the development of dependable software in more concrete terms.In this paper, we describe a systematic approach for the explicit representation of exception handling at key phases in the development of component-based systems. Exceptional behaviour is identified in the use cases of the problem definition, represented by means of idealized fault-tolerant components [4] in the architectural design of the software system, refined as classes and collaborations during des...