2012 IEEE 23rd International Symposium on Software Reliability Engineering Workshops 2012
DOI: 10.1109/issrew.2012.101
|View full text |Cite
|
Sign up to set email alerts
|

A Method to Formally Evaluate Safety Case Evidences against a System Architecture Model

Abstract: For a large and complex safety-critical system, where safety is ensured by a strict control over many properties, the safety information is structured into a safety case. As a small change to the system design may potentially affect a large section of the safety argumentation, a systematic method for evaluating the impact of system changes on the safety argumentation would be valuable.We have chosen two of the most common notations: the Goal Structuring Notation (GSN) for the safety argumentation and the Archi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 3 publications
0
3
0
Order By: Relevance
“…Prior work studied the evolution of safety analyses and assessments [40] and the possible impact of architectural changes in safety cases [3]. Recent models for safety certification explicitly address SECIA needs (e.g., [13]), such as the specification of the effects that a change in an artefact type can have in other types.…”
Section: Impact Analysis For Safety-critical Systemsmentioning
confidence: 99%
See 1 more Smart Citation
“…Prior work studied the evolution of safety analyses and assessments [40] and the possible impact of architectural changes in safety cases [3]. Recent models for safety certification explicitly address SECIA needs (e.g., [13]), such as the specification of the effects that a change in an artefact type can have in other types.…”
Section: Impact Analysis For Safety-critical Systemsmentioning
confidence: 99%
“…In fact, this approach is recommended in some safety standards, explicitly (e.g., Defence Standard 00-56) or implicitly (e.g., EN 50129). Consequently, it would be logical that the median for Safety Cases in Table 3 was higher than "some projects", and that Safety Cases had strong or very strong correlations with more artefact types (e.g., Architecture Specifications, in line with [3]). Albeit "every project" was the mode for Safety Cases in Table 3, 28.8% of the respondents indicated that Safety Cases had never been affected by changes or had been affected in few projects.…”
Section: Reused Components Informationmentioning
confidence: 99%
“…The EU funded project MODSafe provides a risk analysis method purposed to combine potential hazards, safety requirements and functions, and link these elements to a generic functional and object-oriented structure of a guided transport system. The SaferCer project (Björnander, 2012) provides a generic process model for integrated certification and development of component based systems, including an overall picture of the development and verification of components and systems. ASCOS (Roelen, 2014) focuses on safety and certification of new aviation operation and systems, including advices on methods and tools for safety based design.…”
Section: Related Workmentioning
confidence: 99%