1984
DOI: 10.1109/mc.1984.1659054
|View full text |Cite
|
Sign up to set email alerts
|

Software Safety in Computer-Controlled Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

1985
1985
2015
2015

Publication Types

Select...
6
2
1

Relationship

0
9

Authors

Journals

citations
Cited by 51 publications
(6 citation statements)
references
References 19 publications
0
6
0
Order By: Relevance
“…A fail-safe system attempts to limit the amount of damage caused by a failure [5]. No attempt is made to satisfy the functional specifications except where necessary to ensure safety.…”
Section: Dependabilitymentioning
confidence: 99%
“…A fail-safe system attempts to limit the amount of damage caused by a failure [5]. No attempt is made to satisfy the functional specifications except where necessary to ensure safety.…”
Section: Dependabilitymentioning
confidence: 99%
“…While typically applied to a system design, FTA has recently been applied to software to determine how failures in its implementation could cause a hazard (Leveson 1984;Knight & Nakano, 1997). It can be used to determine cases where the implemented design could cause a hazard, or show which modules are most critical to the safe operation of the system.…”
Section: Rehabilitation Roboticsmentioning
confidence: 99%
“…Security attributes add requirements to detect and avoid intentional faults. Safety, see (Leveson, 1984), is the ability to deliver service under given conditions with no catastrophic effects. Safety attributes add requirements to detect and avoid catastrophic failures.…”
Section: Functionality and Dependabilitymentioning
confidence: 99%