An architectural support for self-adaptive software for treating faults
WOSS '02 Proceedings of the first workshop on Self-healing systems
A fault-tolerant software architecture for COTS-based software systems
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
The design and implementation of a self-healing database system
Journal of Intelligent Information Systems - Special issue: Database and applications security
ACM SIGAda Ada Letters
A fault-tolerant software architecture for component-based systems
Architecting dependable systems
A taxonomy of software architecture-based reliability efforts
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Fault injection approach based on architectural dependencies
Architecting Dependable Systems III
| Hi-index | 0.00 |
"Software engineering has produced no effective methods to eradicate latent software faults." This sentence is, of course, a stereotype, but it is as true as a stereotype can get. And yet, it begs some questions. If it is not possible to construct a large software system without residual faults, is it at least possible to construct it to degrade gracefully if and when a latent fault is encountered? This paper presents the approach adopted on CAATS (Canadian Automated Air Traffic System), and argues that OO design and certain architectural properties are the enabling elements towards a true fault-tolerant software architecture.