Skip to content

Component Documentation

Addresses: ISO 26262-8 12.5.1, from 12.4.2.1

The slint-sc runtime ships inside the customer’s binary, so it’s qualified as a software component rather than as a tool. This document is its specification. The Component Qualification Plan says how it’s qualified. The Component Qualification chapter of the Qualification Report records the outcome.

  • Safety Analysis: what can go wrong in the runtime, and the measure or constraint that covers each error.

12.4.2.1 asks the specification of the component to include the following.

ItemWhere
a) Unique identificationThe slint-sc crate from api/slint-sc, of the release under qualification
b) Maximum target ASILASIL B; see Integrity Level
c) Qualification activitiesComponent Qualification Plan
d) Requirements of the componentThe rendering model and the generated code contract, one identified paragraph per requirement
e) Requirements of the intended useUser Manual
f) ConfigurationThe crate has no features and no dependencies, so it has one configuration
g) Interfaces and shared resourcesThe slint-sc Runtime API, and the frame buffer the application owns; see Architecture Design
h) Application manualUser Manual
i) Integration instructionsAdd the Runtime in the User Manual
j) Reactions under anomalous operating conditionsSafety Analysis; a frame buffer of the wrong size is rejected per sls.gen.render-error
k) Known anomalies and workaroundsKnown Problems

© 2026 SixtyFPS GmbH

Built from commit 9e95c298ad7251b85418c922c492cd327464b66c