Conformity according to ISO 26262

for ISO 26262 ASIL-A, ASIL-B, ASIL-C, and ASIL-D

The achievement of functional safety is influenced by the development process (including such activities as requirements specification, design, implementation, integration, verification, validation and configuration), the production and service processes and the management processes.

Axivion Suite especially supports compliance with ISO 26262-6:2018 – product development at the software level. In the V-Model Axivion is used in software unit verification, software integration, and verification and testing of embedded software.

Hier zeigt Axivion den Prozess der Software Integration

Axivion provides a means to: enforce low complexity, use well trusted design principles, use of unambiguous graphical representation, use of language subset, enforcement of strong typing, use of defensive implementation techniques, use of style guides, use of naming conventions and concurrency aspects.

These requirements from ISO 26262-6:2018 are fulfilled by Axivion’s architecture verification, clone detection, cycle detection, dead code analysis, metrics monitoring, stylechecks (MISRA, AUTOSAR C++14, CERT) as well as static and semantic code analysis.

Axivion Suite integrates with almost any CI-System which allows for repeatable and comparable production of software. At the same time Axivion Suite could run also locally allowing for fast checks and short roundtrip times.

Axivion Suite provides architecture verification. Any notation (design/architecture) provided as either, natural language, informal notation or semi-formal notation could be verified with Axivion’s architecture verification against the implementation in C or C++.

Fehlgerichtete Aufrufe zwischen ASIL- und QM-Partitionen werden hier aufgespürt - in Entwicklung und Produktion ist Freedom from Interference eines der wichtigsten Safety Goals.

Freedom from interference is a strong goal in safety projects. Axivion’s architecture verification can help identifying potential violations early on source code level identifying function calls between various ASIL levels and QM. This could help saving time running less frequent into exceptions from the MMU/MPU later in the development cycle.

Depending on customers use cases the Axivion Suite might be classified in the project and hence must be qualified to the respective TCL level. Axivion provides the tool Qualification Kit.

The kit contains a set of violations of MISRA, CERT and AUTOSAR C++14, which allow to qualify customers current setup to any ASIL level and use case.

.

Hier gibt der Use Case des Kunden das tool confidence level (TCL) vor - die Axivion Suite muss entsprechend qualifiziert werden, zum Beispiel um für das Setup für beliebige ASIL Levels qualifiziert zu werden.

A safety analysis with Axivion brings in all the strengths and features of the Axivion Suite such as architecture verification, clone detection, metrics monitoring, styleguides (MISRA, CERT, AUTOSAR C++14), dead code analysis and cycle detection together with the qualification required by the respective TCL by the tool Qualification Kit for any ASIL level.

The Axivion Suite provides us with crucial support when implementing new features in EB street director and guaranteeing the quality of our software solutions in the long term.

 

Jakob Schmidt, Software Architect at Elektrobit