Proceedings of Annual Reliability and Maintainability Symposium (RAMS)
DOI: 10.1109/rams.1994.291130
|View full text |Cite
|
Sign up to set email alerts
|

Rare conditions and their effect on software failures

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Publication Types

Select...
6
4

Relationship

0
10

Authors

Journals

citations
Cited by 32 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…A similar picture emerged from a study of failures during final test of the Space Shuttle Avionics (SSA) software prior to the first re-launch after the Challenger accident [9]. Exceptions are there referred to as rare events, and a rare report is a failure report in which the cause is traced to faulty exception handling.…”
Section: Exception Handling As a Cause Of Failuresmentioning
confidence: 87%
“…A similar picture emerged from a study of failures during final test of the Space Shuttle Avionics (SSA) software prior to the first re-launch after the Challenger accident [9]. Exceptions are there referred to as rare events, and a rare report is a failure report in which the cause is traced to faulty exception handling.…”
Section: Exception Handling As a Cause Of Failuresmentioning
confidence: 87%
“…In previous work we have shown that exception handling is a very frequent cause of failures [12], and not every analyst will consider an exception handling routine as a function. Thus the visibility over exception handling tends to get lost in functional partitioning.…”
Section: Software Fmeamentioning
confidence: 99%
“…One difficult decision here is whether to include software failures in the set of credible failure modes. Since experience has shown that the possibility of software design faults cannot be ignored in large-scale applications [9], AFTM will provide a variety of fault-handling provisions for tolerating both hardware and software faults. However, the application designer will inform AFTM whether software faults should be considered by AFTM or not.…”
Section: Essential Core Attributes Of the Aftm Middlewarementioning
confidence: 99%