1994
DOI: 10.1016/0164-1212(94)90082-5
|View full text |Cite
|
Sign up to set email alerts
|

Assessing traditional verification's effectiveness on safety-critical software systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

1996
1996
2011
2011

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 15 publications
0
2
0
Order By: Relevance
“…This does not follow sound modules. For example, if two human errors are made, safety design principles elaborated in countless references [2], one during segmentation and one during registration, the [5], [7], [9], [10], [11], [12], [17], [18], [19], [20], [21], [22].…”
Section: Introductionmentioning
confidence: 99%
“…This does not follow sound modules. For example, if two human errors are made, safety design principles elaborated in countless references [2], one during segmentation and one during registration, the [5], [7], [9], [10], [11], [12], [17], [18], [19], [20], [21], [22].…”
Section: Introductionmentioning
confidence: 99%
“…The techniques they suggest do not consider safety hazards that are not related to the software and for which software design could provide mitigation and/or removal. This does not follow sound safety design principles elaborated in countless references Chudleigh et al (1995); Elliott et al (1994);Fei et al (2001); Gowen (1995); Gowen & Collofello (1994); Halang et al (1998);Jiang et al (1998);Jones et al (2002); Knight (1990); Leffingwell & Norman (1993); Leveson (1995). Leveson states that "...the quality of a safety program is measured by its ability to influence design" Leveson (1995); this ability comes in the form of safeguard requirements that comes from a safety analysis.…”
Section: Component-based Trusted Architecture Patternmentioning
confidence: 99%