See this document in CiteSeerX!

Predicting When to Reboot "Continuously Operating" Systems  (Make Corrections)  
J. Voas, F. Charron



  Home/Search   Context   Related

 
View or download:
rstcorp.com/pub/papers/finland.ps
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  rstcorp.com/papers/chrono1999 (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: One of the greatest problems associated with embedded control software is knowing how to gracefully handle state corruption that gradually builds up after continuous execution of the software. Our paper presents: (1) an empirical technique for assessing how frequently such systems should be rebooted, and (2) an empirical technique for determining which portions of the state create the greatest safety risks if they are corrupted. Armed with this information, developers and certifiers can create... (Update)

Similar documents (at the sentence level):
8.3%:   Software Hazard Mining - Voas   (Correct)

Active bibliography (related documents):   More   All
0.5:   Dependability Certification of Software Components - Voas, Payne (2000)   (Correct)
0.0:   Instruction Scheduling and Executable Editing - Schnarr, Larus (1996)   (Correct)
0.0:   Fine-Grain Access Control for Securing Shared Resources .. - Butt, Adabala, Fortes, .. (2002)   (Correct)

Similar documents based on text:   More   All
0.2:   Reducing Uncertainty About Common-Mode Failures - Voas, Ghosh, Charron, Kassab (1997)   (Correct)
0.2:   Towards Analyzing Security-Critical Software During.. - Ghosh, McGraw, Charron.. (1996)   (Correct)
0.2:   Can Critical Information Infrastructure Protection be Achieved.. - Voas (1999)   (Correct)

BibTeX entry:   (Update)

@misc{ voas-predicting,
  author = "J. Voas and F. Charron",
  title = "Predicting When to Reboot "Continuously Operating" Systems",
  url = "citeseer.ist.psu.edu/86766.html" }
Citations (may not include all citations):
87   Random Number Generators: Good Ones are Hard to Find (context) - PARK, MILLER - 1988
50   Evaluation of Safety-Critical Software (context) - PARNAS, VAN SCHOUWEN et al. - 1990
38   Fault injection techniques and tools - HSUEH, TSAI et al. - 1997
19   Software Fault Injection: Inoculating Programs Against Error.. (context) - VOAS, MCGRAW - 1998
13   Efficient Run-time Monitoring Using Shadow Processing - PATIL, FISCHER - 1995
2   Using Assertions to Make Untestable Software More Testable - VOAS, KASSAB - 1999
1   Army Records Say Computer Shutdown Might Have Averted Scud D.. (context) - BURNS - 1991

Documents on the same site (http://rstcorp.com/papers/chrono-1999.html):   More
Inoculating Software for Survivability - Ghosh, Voas (1999)   (Correct)
Using Program Behavior Profiles for Intrusion Detection - Ghosh, Schwartzbard, Schatz (1999)   (Correct)
Software Component Dependability Assessment - Voas (1998)   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC