Abstract
The session opens by framing the software specific challenges of in cabin safety critical functions such as driver monitoring, occupant detection, and safety related HMI, highlighting the limitations of document-based workflows for ISO 26262 and ASPICE.
It introduces an MBD centered approach where software safety requirements, software architecture, behavioral logic, interfaces, diagnostics, timing constraints, and safe state handling are modeled and traced across the software side of the V cycle.
The talk then walks through a concise, generic case study for an in-cabin safety function that demonstrates end-to-end traceability in the model from software safety requirements to software design elements and verification artifacts.
The case study showcases integration of complementary tools to satisfy ASPICE SWE process expectations, V cycle alignment from definition through verification, and ISO 26262 software level functional safety, while remaining tool agnostic so that specific products can be substituted.
The session concludes with practical guidance on governing model quality, maintaining bidirectional traceability across requirements, design, code, and tests, preparing for software focused audits, and managing frequent changes without over modeling.
Value
This session provides a tool neutral method for integrating ISO 26262 software activities with ASPICE SWE processes using an MBD driven workflow, demonstrated with an example multi tool integration. Attendees will see how to maintain end to end traceability across the software portion of the V cycle, link formal safety analysis to design and tests, and generate unified evidence for audits.
The patterns for change impact, model organization, and reporting are portable across tool chains, enabling teams working on in cabin safety critical software to reduce duplication and improve verification and compliance regardless of specific product choices.