2020
DOI: 10.1016/j.jestch.2019.09.005
|View full text |Cite
|
Sign up to set email alerts
|

(User-friendly) formal requirements verification in the context of ISO26262

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0
1

Year Published

2020
2020
2023
2023

Publication Types

Select...
3
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 15 publications
0
3
0
1
Order By: Relevance
“…We proposed an approach that exploits behavioral conformance testing to automatically generate, from a formal model and test purposes, scenarios in the form of behavior trees for the Our approach makes possible the formalization (as test purposes) of safety requirements defined in standards, such as ISO 26262, and the generation of test cases, similarly to [17]. The test cases can be used both for producing simulation scenarios (as we illustrated here) and for assessing the correct functioning of AVs in their environment.…”
Section: Discussionmentioning
confidence: 99%
“…We proposed an approach that exploits behavioral conformance testing to automatically generate, from a formal model and test purposes, scenarios in the form of behavior trees for the Our approach makes possible the formalization (as test purposes) of safety requirements defined in standards, such as ISO 26262, and the generation of test cases, similarly to [17]. The test cases can be used both for producing simulation scenarios (as we illustrated here) and for assessing the correct functioning of AVs in their environment.…”
Section: Discussionmentioning
confidence: 99%
“…In this section, we fulfil the goal of extending safety verification to the level of simulation to provide evidence that the system goals are satisfied during operation (Makartetskiy, 2019). We are interested in exploring the impact of the adaptability on the Quality of Service (QoS) with a large number of vehicles.…”
Section: Experimental Validationmentioning
confidence: 99%
“…A wrong determination of the ASIL can result in a system where the residual risk is high in case of system failure, thus not meeting the established metrics for an acceptable risk reduction or that the system is oversized. And other consequences related to unnecessary costs and a longer development time, since requirements generated in this phase will demand verification and validation tests following the development model in V [6].…”
Section: Introductionmentioning
confidence: 99%
“…Uma determinação equivocada do ASIL pode acarretar em um sistema onde o risco residual seja elevado em caso de falha do sistema, não atendendo assim as métricas estabelecidas ou que o sistema esteja superdimencionado. E outras consequências em custos desnecessários e um maior tempo de desenvolvimento quando superestimado, uma vez que requisitos gerados nesta fase demandarão testes de verificação e validação seguindo o modelo de desenvolvimento em V [6].…”
Section: Introductionunclassified