Search Results

Modern cars contain more and more safety-relevant features which require addressing safety aspects during all development phases: on the functional level, on the architectural level, during integration as well as throughout the verification. The workflow of designing safe and reliable automotive embedded systems start with appropriate requirements definitions. According to the automotive safety standard ISO 26262, functional as well as non-functional threats need to be addressed. Non-functional aspects of safe software include a sound and safe timing of the software. The right methods, tools and standards enable OEMs and suppliers developing and providing applications which meet their timing requirements and a high level of quality. We present with this paper some important aspects related to timing in automotive embedded systems as well as the major standards such as TIMMO and AUTOSAR.

This paper outlines the modeling process in SysML (Systems Modeling Language) in context of MBSE (Model Based Software Engineering) as well as the MBD (Model-Based Design) in Simulink and we compare the models to get useful information into software. For this goal, we propose the use of an RM/SM tool (Requirements Management and Systems Modeling) (3SL Cradle) and Matlab/Simulink to model the system, do the system validations, and finally embed the generated code. For automotive systems, the development process is visualized through the V-Model, which leads to the right choice of components, the integration of the system and the project realization. The first step in V-Model handles the requirements management for the development, i.e., the requirements for a project will be collected in respect to the stakeholder’s needs and system limitations.