Search Results

The international standard ISO 26262 for functional safety of road vehicles claims processes and requirements for the entire product lifecycle of automotive electric and electronic systems. The demanded activities and work products within the standard are highly interconnected. Additionally, references to exemplarily external quality management standards or commonly recognized industry sources are given. Therefore, the application of functional safety processes in distributed development is challenging regarding description, understanding, analysis and planning of processes. To overcome these inconveniences, we provide a meta model extension for model-based architecture description languages regarding process description, organizational structures and resource assignment. This is related to the established “Business Process Model and Notation” (BPMN) according to ISO/IEC 19510:2013.

Electronic design on detailed hardware level for automotive safety-related systems requires evaluation of the hardware architecture to cope with random hardware failures. The international standard ISO 26262 - functional safety for road vehicles - claims two methods: hardware architectural metrics and evaluation of safety goal violations as a probabilistic approach. Although the utilization of these analyses is required, annotations of failure data in combination with performing evaluation of a preliminary hardware architecture using deposited failure data is not supported in an integrated model-based development environment. To overcome these inconveniences, we analyzed the ISO 26262, in particular Part 5 for product development at the hardware level, to provide both, meta-model for failure description of detailed hardware and performing evaluation of the hardware architecture. This UML-compliant meta-model expands existing EAST-ADL2 constructs.

Precisely defined terms and metrics as well as a reliable base of information are the foundation for integrated maturity assessment of complex electronic systems. In this paper, a method is proposed for defining and quantifying multiple relations between systems, functions, requirements, and test cases, allowing to improve traceability in the specification documents and to define terms like test progress, test coverage and system maturity formally. The method is based on an extended generic data model replacing commonly used hierarchical data models for storing function specifications and test artifacts. The key feature are allocation matrices for realizing weighted n:m-relations between systems, requirements, and test cases. Theses matrices represent the distributed systems according to the vehicle network architecture, as well as the requirement coverage of the specified test cases.