This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Working IEEE/IFIP Conference on Software Architecture (WISCA'01)
Towards Fault-tolerant Software Architectures
Amsterdam, The Netherlands
August 28-August 31
ISBN: 0-7695-1360-3
ASCII Text
x 
 
Drasko Sotirovski, "Towards Fault-tolerant Software Architectures," Software Architecture, Working IEEE/IFIP Conference on, pp. 7, Working IEEE/IFIP Conference on Software Architecture (WISCA'01), 2001.
 
 
BibTex
x
 
@article{ 10.1109/WICSA.2001.948399,
author = {Drasko Sotirovski},
title = {Towards Fault-tolerant Software Architectures},
journal ={Software Architecture, Working IEEE/IFIP Conference on},
volume = {0},
year = {2001},
isbn = {0-7695-1360-3},
pages = {7},
doi = {http://doi.ieeecomputersociety.org/10.1109/WICSA.2001.948399},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Software Architecture, Working IEEE/IFIP Conference on
TI - Towards Fault-tolerant Software Architectures
SN - 0-7695-1360-3
SP
EP
A1 - Drasko Sotirovski,
PY - 2001
VL - 0
JA - Software Architecture, Working IEEE/IFIP Conference on
ER -
 
Drasko Sotirovski, Raytheon Systems Canada Ltd.
"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.
Citation:
Drasko Sotirovski, "Towards Fault-tolerant Software Architectures," wicsa, pp.7, Working IEEE/IFIP Conference on Software Architecture (WISCA'01), 2001
Usage of this product signifies your acceptance of the Terms of Use.