Recovery oriented programming

Olga Brukman, Shlomi Dolev, Marcelo Sihman

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

Abstract

Computerized management of critical systems makes the issues of correctness and faultless flow of long-lived and continuously-running programs extremely important e.g., [6, 7]. Complex systems cannot be fully verified because their verification may require an unreasonable amount of time and space. The software industry tests software products extensively in order to eliminate bugs as much as possible. Normally, software is tested by executing a set of large, but length-bounded and non-exhaustive scenarios starting from a predefined initial state while each scenario is defined by a set of input/output sequences. Undesired and unplanned behavior (bug) may occur due to scenarios that were not tested prior to the software release. Software malfunctions may cause damage that can outweigh the software cost. Keeping all this in mind, a consumer of a critical system would like to have a warranty that such a system will operate properly.

Original languageEnglish
Title of host publicationProceedings of the 20th ACM Symposium on Operating Systems Principles, SOSP 2005
DOIs
StatePublished - 1 Dec 2005
Event20th ACM Symposium on Operating Systems Principles, SOSP 2005 - Brighton, United Kingdom
Duration: 23 Oct 200526 Oct 2005

Publication series

NameProceedings of the 20th ACM Symposium on Operating Systems Principles, SOSP 2005

Conference

Conference20th ACM Symposium on Operating Systems Principles, SOSP 2005
Country/TerritoryUnited Kingdom
CityBrighton
Period23/10/0526/10/05

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Recovery oriented programming'. Together they form a unique fingerprint.

Cite this