Software architecture for self-healing of concurrent and distributed components

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

This paper describes a self-healing component architecture that is able to detect object anomalies in the component, reconfigure inter-component and intracomponents before and after repairing the sick object, repair it, and then test the healed object. A distributed and concurrent component is structured to tasks (active objects), connectors, and passive objects accessed by tasks. Each self-healing component is designed with two layers: the service layer and healing layer. The service layer of a component provides functional services to the other components, whereas the healing layer monitors objects in the service layer and repairs the sick objects detected. In addition, this paper describes constituents of the healing layer of a concurrent and distributed component, which include the Component Repair and Reconfiguration Controller (CRRC), Component Monitor, Component Repair and Reconfiguration Plan (CRRP), and Component Repair and Reconfiguration Executor. To illustrate this approach, the elevator system is considered.

Original languageEnglish
Title of host publicationProceedings of the International Conference on Software Engineering Research and Practice, SERP'04
EditorsH.R. Arabnia, H. Reza
Pages97-103
Number of pages7
StatePublished - 2004
EventProceedings of the International Conference on Software Engineering Research and Practice, SERP'04 - Las Vegas, NV, United States
Duration: Jun 21 2004Jun 24 2004

Publication series

NameProceedings of the International Conference on Software Engineering Research and Practice, SERP'04
Volume1

Conference

ConferenceProceedings of the International Conference on Software Engineering Research and Practice, SERP'04
Country/TerritoryUnited States
CityLas Vegas, NV
Period06/21/0406/24/04

Fingerprint

Dive into the research topics of 'Software architecture for self-healing of concurrent and distributed components'. Together they form a unique fingerprint.

Cite this