Search Results

Model-Based Development processes in the automotive industry typically use high-level modeling languages to build the reference models of embedded controllers. One can use formal verification tools to exhaustively verify these design models against their requirements, ensuring high quality models and a reduction in the cost and effort of functional testing. However, there is a gap, in terms of processes and tools, between the informal requirements and the formal specifications required by the verification tools. In this paper, we propose an approach that tries to bridge this gap by (i) identifying the verifiable requirements through a categorization process, (ii) providing a set of templates to easily express the verifiable requirements, and (iii) generating monitors that can be used as specifications in design verification tools. We demonstrate our approach using the Simulink Design Verifier tool for design verification of Simulink/Stateflow models.

Automotive HW/SW architectures are becoming increasingly complex to support the deployment of new safety, comfort, and energy-efficiency features. Such architectures include several software tasks (100+), messages (1000+), computational and communication resources (70+ CPUs, 10+ buses), and (smart) sensors and actuators (20+). To cope with the increasing system complexity at lowest development and product costs, highest safety, and fastest time to market, model-based rapid-prototyping development processes are essential. The processes, coupled with optimization steps aimed at reducing the number of software and hardware resources while satisfying the safety requirements, enable reduction of the system complexity and ease downstream testing/validation efforts. This paper describes a novel model-based design exploration and optimization process for the deployment of a set of software tasks on a dual-processor control module implementing a fail-safe strategy.