Application of the Upcoming SPDX Safety Profile
summary
Proposes using the upcoming SPDX 3.1 Safety Profile to model and automate traceability across requirements, design, tests and build artifacts so Excel lists go away; implements SPDX relationships and enums to map the V model as a knowledge graph, enables impact analysis and reproducible change assessment, and supports creating a Safety SBOM and passing a build SBOM that contains relationship to a source SBOM; no full tooling yet but several proof‑of‑concepts and early implementations exist.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Functional safety importance
- 5:00Systematic capability explained
- 8:12Manual safety documentation challenges
- 10:00SPDX safety profile benefits
- 12:25Automating safety documentation
- 13:31Model-based safety advantages
- 14:14Contributing to SPDX safety
- 22:55Who needs SPDX safety
- 24:21Q&A
related talks
43mExtending SBOMs to Describe AI Systems
27mHow Software Transparency Can Help Save the World
15mFrom SBOM to Dependency Stacks: Making Software Structure Visible
30mTransparency in the Software Supply Chain: Making SBOM a Reality
36mSW360 SBOM: Managing Vulnerability Information, SPDX Documents and New Depen...
35mSBOMs: Navigating the Evolving Landscape of Software Bill of Materials
46mAn SBOM Primer: From Licenses to Security, Know What’s in Your Code, or Someone Else’s!
28mGenerating SBOMs for IoT at Build Time