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.

A key requirement for the development of safety-critical systems is the correctness of the tools used in their development process. Standards such as DO-178B mandate the qualification of tools used in the software engineering process of the systems to be certified at the highest levels of criticality. On the other hand, the increasing complexity of software requires the use of methodologies such as Model Based Development (MBD) that are highly tool intensive. MBD employs a suite of tools such as model-translators, code-generators, optimizers, simulators, etc., that can collectively be referred to as model-processors. A model-processor accepts a model in one language, and outputs a processed model in a possibly different language. Due to the increasing sophistication in modern modeling languages, model-processors are prone to implementation errors. Also, they are continuously evolving, resulting in differences in their behaviour across different releases.