Formal Verification of Automotive Simulink Controller Models: Empirical Technical Challenges, Evaluation and Recommendations

Nellen, Johanna; Rambow, Thomas; Waez, Tawhid Bin; Ábrahám, Erika; Katoen, Joost-Pieter

doi:10.1007/978-3-319-95582-7_23

Cited by 5 publications

(7 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Our works relies on the pattern catalogs from [7,1]. Inspired by our experience with Ford [19,2], we selected a set of patterns that covers more than 90% of our investigated automotive requirements.…”

Section: Related Workmentioning

confidence: 99%

“…The industry standard ISO26262 recommends formal verification to ensure that such safety-critical software is implemented in accordance with the functional requirements. The work of our previous two papers [19,2] and this paper not only applies to safety critical automotive software but also to quality management (QM) or non-safety critical automotive software. In fact, we worked only on Ford QM software features in our papers.…”

Section: Introductionmentioning

confidence: 99%

“…In our previous works [19,2], we considered an MBD process starting with the development of Simulink controller models and using Simulink's code generation functionality to derive C code for software units. For formal verification, we analyzed the feasibility of both Simulink Design Verifier (SLDV ) for Simulink models as well as BTC EmbeddedPlatform verification tool for the generated C code.…”

Section: Introductionmentioning

confidence: 99%

“…For formal verification, we analyzed the feasibility of both Simulink Design Verifier (SLDV ) for Simulink models as well as BTC EmbeddedPlatform verification tool for the generated C code. Our papers [19,2] present our observations and give recommendations for requirement engineers, model developers and tool vendors how they can contribute to a formal verification process that can be smoothly integrated into MBD.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

Berger¹,

Nellen²,

Katoen³

et al. 2019

Preprint

Self Cite

View full text Add to dashboard Cite

In industrial model-based development (MBD) frameworks, requirements are typically specified informally using textual descriptions. To enable the application of formal methods, these specifications need to be formalized in the input languages of all formal tools that should be applied to analyse the models at different development levels. In this paper we propose a unified approach for the computer-assisted formal specification of requirements and their fully automated translation into the specification languages of different verification tools. We consider a two-stage MBD scenario where first Simulink models are developed from which executable code is generated automatically. We (i) propose a specification language and a prototypical tool for the formal but still textual specification of requirements, (ii) show how these requirements can be translated automatically into the input languages of Simulink Design Verifier for verification of Simulink models and BTC EmbeddedValidator for source code verification, and (iii) show how our unified framework enables besides automated formal verification also the automated generation of test cases.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Multiple Analyses, Requirements Once: simplifying testing & verification in automotive model-based development

Berger¹,

Nellen²,

Katoen³

et al. 2019

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

“…Этот подход больше соответствует предметным областям, в которых требования к функциональности могут быть относительно простыми, но требование к надежности и безопасности стоит во главе угла. Примерами таких областей могут быть авионика [5; 6], медицина [7], автомобильная промышленность [8], разработка распределенных вычислительных программ [9] и аппаратного оборудования в соответствии с индустриальными стандартами [10].…”

Section: формальная верификацияunclassified

Developing Web-Application’s Automated Testing Technique

Ткачев

Irtegov

2019

JIT

View full text Add to dashboard Cite

The article is devoted to the technique of automated testing of NSUts – automatic assessment system for programming tasks developed at NSU. The main priority for this technique is to test both the old and the new versions of the application, so that the same or minimally modified tests could be executed on two versions of the system with different architectures. This could be useful while organizing the development process for other applications with a long life cycle. To test not only the server but also the client side of the web application, we suggest using tools like Selenium WebDriver to simulate user actions by sending commands to real browsers. We use the well-known Page Object design pattern to handle differences in HTML layout and functionality, and describe a number of ways to make developed tests less fragile and easily adapt those to work with the new version of the system. The article also describes the use of this technique to organize automated testing of the NSUts system and analyzes its effectiveness. The analysis shows that the estimated code coverage by these tests is quite high, and therefore the technique can be considered effective and applied to other similar web applications.

show abstract