Tool Evaluation Report

Addresses: ISO 26262-8 11.5.1, from 11.4.1 to 11.4.5

This report evaluates the tools Slint SC provides: the Slint compiler and slint-sc-coverage. Neither ships in the product, but the compiler writes code that does, and slint-sc-coverage produces evidence. The runtime ships, so it’s not a tool; the Component Documentation covers it.

• Use Cases: how each tool is used in a project.
• Potential Errors: what can go wrong in each tool, and the measure or constraint that covers each error.
• Tool Classification: the confidence level each tool needs, derived from the potential errors and their detection.
• Qualification Method: how each tool reaches that confidence.

The outcome of the qualification is in the Tool Qualification chapter of the Qualification Report.

Planning of Usage

11.4.4.1 asks for the usage of each tool to be planned.

	Slint compiler	slint-sc-coverage
a) Identification and version	slint-compiler from tools/compiler, of the release under qualification	slint-sc-coverage from tools/slint-sc-coverage, of the release under qualification
b) Configuration	Built with the slint-sc feature, invoked with --slint-sc	Given the .slintcov maps the compiler writes with --coverage, and an llvm-cov export
c) Use cases	UC_COMPILE_SLINT_FILE	UC_MEASURE_SLINT_COVERAGE
d) Environment	The build host	The build host, where the LLVM profiler runtime is available
e) Maximum ASIL	ASIL B, assumed; see Integrity Level	ASIL B, assumed
f) Qualification methods	Validation	Validation

The maximum ASIL is an assumption, since Slint SC is developed out of context. 11.4.2 asks the integrator to verify it before using the tools on their item.

Available Information

11.4.4.2 asks for this information to be available:

Information	Where
a) Features, functions, and technical properties	Reference, and Coverage of Slint Code
b) User manual	User Manual
c) Environment required for operation	Use Cases
d) Behavior under anomalous operating conditions	The compiler rejects everything outside the qualified subset with a diagnostic; see Test Suites
e) Known malfunctions, and safeguards	Known Problems
f) Measures that prevent or detect malfunctions	Potential Errors

TODO

State the environment requirements of both tools, including the supported host platforms. Describe how slint-sc-coverage behaves under anomalous conditions, such as a map written for other code.