loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Designing for Recovery
July/August 2006 (vol. 23 no. 4)
pp. 11-13
ASCII Text
x 
 
Rebecca Wirfs-Brock, "Designing for Recovery," IEEE Software, vol. 23, no. 4, pp. 11-13, July/August, 2006.
 
 
BibTex
x
 
@article{ 10.1109/MS.2006.98,
author = {Rebecca Wirfs-Brock},
title = {Designing for Recovery},
journal ={IEEE Software},
volume = {23},
number = {4},
issn = {0740-7459},
year = {2006},
pages = {11-13},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.98},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Designing for Recovery
IS - 4
SN - 0740-7459
SP11
EP13
EPD - 11-13
A1 - Rebecca Wirfs-Brock,
PY - 2006
KW - software recovery
KW - failing fast
VL - 23
JA - IEEE Software
ER -
 
When things go right, software hums along like well-oiled machinery--receive an event, twiddle with inputs, send a flurry of messages, change the system state, interact with the environment or users, then wait for the next chunk of work. Smooth. Mechanical. Predictable. But what happens when something goes wrong? How should you design your software to detect, react, and recover from exceptional conditions?
Index Terms:
software recovery, failing fast
Citation:
Rebecca Wirfs-Brock, "Designing for Recovery," IEEE Software, vol. 23, no. 4, pp. 11-13, July/Aug. 2006, doi:10.1109/MS.2006.98
Usage of this product signifies your acceptance of the Terms of Use.