Model-based adaptation for self-healing systems

Abstract

Traditional mechanisms that allow a system to detect and recover from errors are typically wired into applications at the level of code where they are hard to change, reuse, or analyze. An alternative approach is to use externalized adaptation: one or more models of a system are maintained at run time and external to the application as a basis for identifying problems and resolving them. In this paper we provide an overview of recent research in which we use architectural models as the basis for such problem diagnosis and repair. These models can be specialized to the particular style of the system, the quality of interest, and the dimensions of run time adaptation that are permitted by the running system.

The Challenge of Self-adaptive Systems for E-commerce

“…Examples of higher-level specifications of (parts of) business collaborations include FMEC (Kimbrough and Moore 1997), the layered approach of (Weigand and Van den Heuvel 1999) and the contract language BCL (Linington et al, 2004). The advantage of such a high-level specification is similar to the advantage of ''architecture model-based'' approach advocated in the self-adaptive system literature (Garlan and Schmerl 2002;Valetto and Kaiser 2002) and the MDA approach (Kleppe, Warmer and Bast 2003) in the field of interoperable systems.…”

Supporting crime detection and operational planning with soft systems methodology and viable systems model

“…Whilst the generic framework may look similar to the Lancaster Model it should be noted that Steps 4 and 5 fully incorporate new functionality whilst still ensuring that the philosophies that underpin SSM and VSM are not compromised (Veryard, 1985;LedecZi et al, 2000;Garlan, 2002;Badr, 2003).…”

Self-healing strategies for component integration faults

“…Examples include reconfigurable architectures [14,13], service-discovery mechanisms [10], resources provisioning [28], and different kinds of component reboots [5]. These techniques attempt to address healing of faults without requiring a-priori knowledge of the target applications.…”

“…It has been frequently experienced when servers initialize or when applicationsserialize/deserialize arrays of objects (see for instance the fault description for Hibernate 13 ). A ClassNotFoundException is usually raised when a classloader cannot find the class definition or fetch the byte codes from the source.…”