Architectural style requirements for self-healing systems

Mikic-Rakic, Marija; Mehta, Nikunj R.; Medvidović, Nenad

doi:10.1145/582128.582138

Cited by 48 publications

(17 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…More generally, to achieve self-healing in software systems, an architectural style needs to meet certain requirements [85], which include adaptability, dynamicity, awareness, autonomy, robustness, distributability, mobility and traceability. These requirements support the four phases of a self-adaptive software life cycle which consists of monitoring, planning the necessary changes, deploying change descriptions and enacting the changes.…”

Section: Surveymentioning

confidence: 99%

Self-healing and self-repairing technologies

Frei

McWilliam

Derrick

et al. 2013

Int J Adv Manuf Technol

View full text Add to dashboard Cite

This article reviews the existing work in selfhealing and self-repairing technologies, including work in software engineering, materials, mechanics, electronics, MEMS, self-reconfigurable robotics, and others. It suggests a terminology and taxonomy for self-healing and selfrepair, and discusses the various related types of other self-* properties. The mechanisms and methods leading to selfhealing are reviewed, and common elements across disciplines are identified.

show abstract

Section: Surveymentioning

confidence: 99%

Self-healing and self-repairing technologies

Frei

McWilliam

Derrick

et al. 2013

Int J Adv Manuf Technol

View full text Add to dashboard Cite

show abstract

“…Prism-MW uses a set of core classes to represent the basic architectural elements: Architecture, Component, Connector, and Port. It also provides an explicit extension mechanism (via Java's abstract classes and interfaces) to implement specific variants of these elements for use in different application scenarios and architectural styles [8,7]. We use Prism-MW, and rely particularly on its extensibility mechanisms and native support for architectural styles, in our approach as discussed below.…”

Section: Related Workmentioning

confidence: 99%

Injecting software architectural constraints into legacy scientific applications

Woollard

Mattmann

Medvidović

2009

2009 ICSE Workshop on Software Engineering for Computational Science and Engineering

Self Cite

View full text Add to dashboard Cite

While software architectures have been shown to aid developers in maintenance, reuse, and evolution as well as many other software engineering tasks, there is little language-level support for these architectural concepts in legacy programming languages such as Fortran and C. Because many existing scientific codes are written in legacy programming languages, it is difficult to integrate them into architected software systems. By wrapping these scientific codes in architecturally-aware Java interfaces, we are able to componentize legacy programs, integrating them into systems built with first-class architectural elements while meeting the performance and throughput requirements of scientific codes.

show abstract

“…Research carried out over the past decade has demonstrated that software architectures can be particularly effective in this capacity [14,16,27].Architectures provide a high-level view of the system, reducing the complexity of understanding what the system is doing, and supporting scalability to complex distributed systems. Suitably annotated architectures also permit the autonomic decision-making apparatus to detect the presence of systemic problems and trends, such as degraded performance.…”

Section: Introductionmentioning

confidence: 99%

Architecture-Based Run-Time Fault Diagnosis

Casanova

Schmerl

Garlan

et al. 2011

Software Architecture

View full text Add to dashboard Cite

Abstract. An important step in achieving robustness to run-time faults is the ability to detect and repair problems when they arise in a running system. Effective fault detection and repair could be greatly enhanced by run-time fault diagnosis and localization, since it would allow the repair mechanisms to focus adaptation effort on the parts most in need of attention. In this paper we describe an approach to run-time fault diagnosis that combines architectural models with spectrum-based reasoning for multiple fault localization. Spectrum-based reasoning is a lightweight technique that takes a form of trace abstraction and produces a list (ordered by probability) of likely fault candidates. We show how this technique can be combined with architectural models to support run-time diagnosis that can (a) scale to modern distributed software systems; (b) accommodate the use of black-box components and proprietary infrastructure for which one has neither a specification nor source code; and (c) handle inherent uncertainty about the probable cause of a problem even in the face of transient faults and faults that arise only when certain combinations of system components interact.

show abstract

Architectural style requirements for self-healing systems

Cited by 48 publications

References 23 publications

Self-healing and self-repairing technologies

Self-healing and self-repairing technologies

Injecting software architectural constraints into legacy scientific applications

Architecture-Based Run-Time Fault Diagnosis

Contact Info

Product

Resources

About