ISO 26262-6:2018: Product development at the software level

Learn how software safety requirements are specified and derived from technical safety requirements, allocated to hardware and software, and decomposed for verification and testing within ISO 26262-6.

Details software architectural design as the second design step, aligning modular, low-complexity units (torque calculation, torque coordinator) with safety requirements, and using notations from natural language to formal, input-logic-output structure.

Explore software unit designs for brake status: one reads can signals and outputs brake pedal ratio; the other uses checksums and counters to derive brake status from can messages.

The lecture outlines error detection and reaction mechanisms for software safety analysis in ISO 26262. It covers input and output checks, plausibility, data error detection, watchdog monitoring, and redundancy.

Define the final step of software unit design and implementation within the software level product development model, emphasizing abstraction for testability and maintainability and modal-based development with tool qualification.

Describe software unit design with function descriptions, calculations, and range checks for brake status based on pedal ratio, mapping pressed states to external brake status via assignments.

Adopt a model-based solution from ETA's, part of Bosch, to design software units with parameters, memory locations, and operators, auto-generating code with checks and optimizations to reduce manual errors.

Assess how to qualify software tools under ISO 26262 clause 11, determining tool confidence levels from tool impact and error detection, and select appropriate qualification methods.

derive test cases for software unit testing in ISO 26262-6:2018 by analyzing requirements, equivalence classes, and boundary value analysis to verify design, robustness, and hardware-software interfaces.

Apply recommended test methods for software units, including statement coverage, branch coverage, and modified condition decision coverage, with ASL-based structural coverage and ACE ratings and SLC.

Explore software integration and testing in ISO 26262-6:2018, verifying embedded software realizes the architectural design, demonstrates compliance with software and hardware interfaces, and checks unit functionality and robustness.

Learn how ISO 26262-6 tests embedded software using hardware-in-the-loop setups, real-time simulators, and vehicle-network environments to verify safety requirements, including test benches, mule vehicles, and rest-of-bus simulations.

Explore the ISO 26262-6 three-level monitoring concept, detailing level one functional functions, level two monitoring, and level three hardware monitoring, and how software monitoring reduces risk in engine control units.

Explore the system definition according to Egas for gasoline engines and electric motors, detailing how accelerator and brake signals drive torque calculation, safety goals, and the three-level monitoring concept.

Analyze torque path monitoring in software, where level two validates level one torque against safety limits to prevent unintended acceleration, using the input, processing and output flow, sensors, and actuators.

Explore torque path monitoring functions, including receive and pre-processing of fieldbus signals, accelerator pedal plausibility, drive mode changes, torque calculation, ESP interventions, and central error management.

Derive software safety requirements and the software architectural design for ISO 26262-6:2018. Explore the history and general aspects of functional safety.

Explore bonus content on ISO 26262-6:2018 software-level product development, highlighting core concepts and practical considerations for compliant software processes.