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

A Model-Driven Safety Certification Method for Process Compliance

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

2014
2014
2020
2020

Publication Types

Select...
5
2
1

Relationship

2
6

Authors

Journals

citations
Cited by 38 publications
(15 citation statements)
references
References 13 publications
0
15
0
Order By: Relevance
“…The idea is to build on top of MDSafeCer [17] and THRUST [27] and provide support for semi-automatic generation of pieces of safety case lines from process lines. We also plan to consider quadrant X,Y, and based on what presented by Sljivo et al [21], generate safety case fragments from product-based information, more specifically contract-based architectural models.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…The idea is to build on top of MDSafeCer [17] and THRUST [27] and provide support for semi-automatic generation of pieces of safety case lines from process lines. We also plan to consider quadrant X,Y, and based on what presented by Sljivo et al [21], generate safety case fragments from product-based information, more specifically contract-based architectural models.…”
Section: Discussionmentioning
confidence: 99%
“…In the long run, however, by assuming that that all the dependencies, especially the safety-critical ones, can be traced and managed, it offers appealing advantages. Single safety cases (related to single products developed according specific single processes), for instance, can be derived in a rather straightforward manner, by applying MDSafeCer [17]. After having configured a product and its corresponding process, the corresponding safety case can be obtained by pruning the safety case line in accordance with the choices performed during the product as well as process configuration.…”
Section: Anti-sisyphus Overviewmentioning
confidence: 99%
“…However, this pattern is not exhaustive and does not identify specific confidence factors. Similar pattern for process-based arguments have also been proposed using model-driven safety certification approaches [19]. By combining this approach of a secondary confidence argument with the various factors that influence the assessor's confidence, we propose a more exhaustive pattern that covers the specific reasons for having confidence in the evidence.…”
Section: Related Workmentioning
confidence: 91%
“…The reason is that ISO 26262-8:11.4.6 states that a tool developed according to the DO330 standard can be considered sufficient for being suitable for ISO 26262 ASIL-D projects. The interested reader may refer to [17] for further details on the standards comparison. Figure 4 represents the SPEM 2.0/EPF-based safety oriented tool qualification process line.…”
Section: A Cross-domain Tool Qualification Process Linementioning
confidence: 99%