2005
DOI: 10.1007/11589976_9
|View full text |Cite
|
Sign up to set email alerts
|

An Automated Failure Mode and Effect Analysis Based on High-Level Design Specification with Behavior Trees

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
45
0

Year Published

2005
2005
2021
2021

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 39 publications
(45 citation statements)
references
References 14 publications
0
45
0
Order By: Relevance
“…The support for timing and performance analysis of DBT is also being investigated. In related work, an automated failure mode and effect analysis is being developed to support safety analysis in the GSE method [12].…”
Section: Resultsmentioning
confidence: 99%
See 2 more Smart Citations
“…The support for timing and performance analysis of DBT is also being investigated. In related work, an automated failure mode and effect analysis is being developed to support safety analysis in the GSE method [12].…”
Section: Resultsmentioning
confidence: 99%
“…In the SAL environment a number of tools provide support for abstraction, program analysis, theorem proving and, model checking. A detailed description of SAL translation rules is provided in [12]. Figure 3 provides a simple example of BT translation into SAL specification.…”
Section: Model Checkingmentioning
confidence: 99%
See 1 more Smart Citation
“…The aim of slicing is to reduce (prior to model checking) a large model to a bisimilar slice which can be model checked instead of the original model, to combat the state explosion problem inherent to model checking. Based on our past experience in the domain of safety analysis, e.g., [8,9,10] we found that there are many cases in which the temporal logic formula of interest includes the next-step operator, and hence these formulas must be preserved by the slice. In the second part of this paper we introduce the resulting new slicing approach for the Behavior Tree modelling notation which is a graphical formal notation that supports the user in capturing informal requirements [11,12].…”
Section: Introductionmentioning
confidence: 99%
“…BT diagram provides a possibility to semi-automatic check of requirements' consistency, completeness, and aliveness [8]. Moreover, if the check process produces some counter examples, it is also possible to trace the counter example visually from the original diagram.…”
Section: Introductionmentioning
confidence: 99%