Qualification Plan

The Qualification Plan describes how Slint SC is organized, designed, developed, and verified.

What can go wrong, and what we do about it, is in the Tool Evaluation Report and the Component Documentation. The evidence from running the tests is in the Qualification Report.

Scope

• Standards Compliance: the standard Slint SC targets, the integrity level it’s developed for, and which chapter addresses each clause.
• Safety Policy: what we commit to, and who is responsible for it.

Design

• Architecture Design: the units that make up Slint SC, and how they fit together at build time and at run time.

Process

• Development Process: the tools, configuration management, and change management.
• Development Phases: the phases a change goes through, and what must hold before it merges.
• Coding Standards: the rules the Rust code follows, and what enforces each one.

Verification

• Verification: what is verified, and the pass criteria.
• Test Suites: the suites that verify Slint SC, and how their cases are written.
• Coverage Criteria: how code coverage is measured, and the level we hold it at.
• Coverage Tool Verification: how the tool that measures the coverage of .slint code is tested.

Qualification

• Component Qualification Plan: how the runtime is qualified as a software component. How the tools are qualified is in the Tool Evaluation Report.