Detailed Description

Safety cases

One safety case per assessment unit of docs/safety/CERTIFICATION_PLAN.dox section 2.1, as Word documents. Structure follows EN 50129 (definition of the system, quality management, safety management, technical safety report, related safety cases, conclusion) with the claims-argument-evidence table in section 5.

Document	Unit	Products
SC-01_Platform_core.docx	Platform core	Platform_RTE, Platform_OS_POSIX
SC-02_Safe_communication.docx	Safe communication	Platform_Protocol_SafeComm
SC-03_RTE_composition.docx	RTE (composition)	Platform core + safe communication
SC-04_Generic_product_RBC_GP.docx	Generic product	RBC_GP
SC-05_Generic_application_RBC_GA.docx	Generic application	RBC_GA
SC-06_Specific_application_RBC_SA.docx	Specific application (template)	RBC_SA

Status: DRAFT, nothing here is assessed. Every claim is marked SUPPORTED, PARTLY or GAP against evidence that exists in the repositories; a claim without evidence is a GAP, never assumed.

Regenerate after the repositories change (the baseline table reads the current git commits):

python3 -m venv .venv && .venv/bin/pip install python-docx

.venv/bin/python build_safety_cases.py

sc_content.py holds the content, sc_builder.py the layout. In Word, press F9 to update the table of contents.