Skip to content

Evidence for regulated products

A team that puts a Kokeb component into a regulated product (a medical device, an industrial safety function, a vehicle) has to show its own regulator or assessor what the component is, how it was verified and what is known to be wrong with it. Each release of a high or safety component publishes that evidence, generated by CI from the same checks that guard every pull request, so it cannot drift from the code.

What each release carries

Item high safety Produced by
Exact identification: version, commit, tag, build inputs ✓ ✓ release workflow
Checksums (SHA256SUMS) and build provenance ✓ ✓ release workflow
SBOM (SPDX) of everything the component contains or pulls in ✓ ✓ release workflow
Rules that applied, and the result of every check ✓ ✓ conformance workflow
Deviation records and active waivers ✓ ✓ conformance workflow
Test report: every test, its result, on which compilers and targets ✓ ✓ host and cross builds
Coverage report, lines and branches ✓ ✓ coverage job
Static analysis results (clang-tidy, cppcheck) ✓ ✓ lint jobs
Requirements and their trace to code and to tests ✓ traceability check
Justification of every uncovered branch ✓ maintainers, checked for completeness
MISRA compliance summary and the commercial checker's report ✓ compliance matrix and checker run
Known anomalies: every open defect that affects the release, with its impact ✓ issue tracker export
Signature over the whole package ✓ release workflow

Requirements and traceability (safety)

A safety component keeps its requirements in docs/requirements.yml, one entry per requirement with an ID (REQ-<component>-NNN), the statement, and its source (datasheet section, standard clause, or design decision). Code and tests point at requirement IDs in comments (// Implements: REQ-XMPL100-012, // Verifies: REQ-XMPL100-012). The traceability check fails when a requirement has no implementing code or no verifying test, or when code or a test cites an ID that does not exist.

Known anomalies

Open defects live as GitHub issues labelled bug. At release, the open ones that affect the released code are exported with their impact and workaround, which is what a manufacturer's evaluation of known anomalies in off-the-shelf software (IEC 62304 7.1.3) asks for.