2003
DOI: 10.1016/s0065-2458(03)58006-8
|View full text |Cite
|
Sign up to set email alerts
|

Software Fault Tolerance Forestalls Crashes: To Err Is Human; To Forgive Is Fault Tolerant

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2006
2006
2009
2009

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 14 publications
0
2
0
Order By: Relevance
“…Nevertheless, as an abstract, intangible entity, software does not wear out with time and usage and become failure prone as hardware; instead, software faults are most often caused by design shortcomings or coding mistakes [16], and are much more difficult to pin down and control [2]. In consequence, for emergency software maintenance, it is hard to classify maintenance functions by levels, assign responsibilities for maintenance functions to a specific level, assign maintenance tasks that are consistent with the scope and range of work to be performed, and accomplish maintenance tasks by ensuring optimum use of resources.…”
Section: Emergency Maintenance Frameworkmentioning
confidence: 99%
“…Nevertheless, as an abstract, intangible entity, software does not wear out with time and usage and become failure prone as hardware; instead, software faults are most often caused by design shortcomings or coding mistakes [16], and are much more difficult to pin down and control [2]. In consequence, for emergency software maintenance, it is hard to classify maintenance functions by levels, assign responsibilities for maintenance functions to a specific level, assign maintenance tasks that are consistent with the scope and range of work to be performed, and accomplish maintenance tasks by ensuring optimum use of resources.…”
Section: Emergency Maintenance Frameworkmentioning
confidence: 99%
“…Bernstein [14] [20], error masking [22,25], fault recovery [24], error detection [19,28] and correction [23] and so on by using necessary replicated data or code, assertions, time or space redundancy etc. Such techniques normally rely on enhanced single version programming (ESVP) schemes [25] that are based on single robust design only.…”
Section: Critical Issues and Possible Solutionmentioning
confidence: 99%