Standards Compliance

This chapter names the standard Slint SC targets and the integrity level it’s developed for. It then maps each clause to the chapter that addresses it.

Standard in Scope

Slint SC targets ISO 26262:2018 at ASIL B. Every clause number in this package refers to that edition.

Nothing in this package is specific to one application domain. Slint SC renders a safety-related user interface; what that interface controls or reports is the integrator’s concern.

Safety Requirements

Addresses: ISO 26262-8 Clause 6

The standard tells us what properties a safety-critical system must have (traceability, freedom from interference, determinism, etc.), but it doesn’t tell us how to write those requirements for a GUI toolkit.

Slint SC states them in two places. The Language Specification says what the language and the runtime must do, one identified paragraph at a time, and each paragraph is traced to the tests that verify it. The Tool Evaluation Report and the runtime’s Safety Analysis say what can go wrong instead, and what detects or constrains each of those.

Integrity Level

Slint SC is a Safety Element out of Context (SEooC). It’s developed without a specific application function, so it has no integrity level of its own to derive. Instead it’s developed to be capable of ASIL B, and the integrator confirms that level is the one their application needs.

ASIL (Automotive Safety Integrity Level) describes the risk level of something. ASIL D=highest, C=high, B=medium, A=low risk, QM = not safety critical. Without an application function there’s no HARA (Hazard Analysis and Risk Assessment) to derive an ASIL from, so ASIL B is a target rather than a result.

Where an application isn’t safety related at all, the full Slint framework can be used instead, and none of this applies.

ISO 26262 Clause Map

Clause	Topic	Where
ISO 26262-2 Clause 6	Confirmation measures	Confirmation Measures
ISO 26262-4 Clause 8	Safety validation	At the vehicle level, so it belongs to the integrator. See User Responsibility. Our own verification is in Verification.
ISO 26262-6 Clause 7	Software architectural design	Architecture Design, and the Safety Analysis of 7.4.10
ISO 26262-8 Clause 5	Distributed development	Distributed Development
ISO 26262-8 Clause 6	Safety requirements	Safety Requirements. 6.4.3.2 asks each safety requirement to reference its source one level up, what realizes it one level down, and the verification specification that checks it.
ISO 26262-8 Clause 7	Configuration management	Configuration Management
ISO 26262-8 Clause 8	Change management	Change Management, and Development Phases for the change workflow itself.
ISO 26262-8 9.4	Verification	Verification
ISO 26262-8 Clause 11	Confidence in software tools	The criteria evaluation report of 11.5.1 is the Tool Evaluation Report. The qualification report of 11.5.2 is Tool Qualification.
ISO 26262-8 Clause 12	Qualification of software components	The plan of 12.4.1 e is the Component Qualification Plan. The documentation of 12.5.1 is the Component Documentation. The qualification report of 12.5.2 is Component Qualification.
ISO 26262-8 Clause 13	Evaluation of hardware elements	Out of scope: Slint SC is software only, so evaluating the hardware it runs on is the integrator’s responsibility.