Traceability and Automation Examples With Basil
summary
Demonstrates BASIL as a code‑centric quality management system that maps requirements to source code and upstream test cases, stores versioned mappings (component versions = workitem + mapping), generates SPDX JSON, and executes tests via TMT into Fedora containers or SSH targets with results linked to bugs. Shows automation using the BASIL HTTP API to scan manpages, match LTP tests, auto‑fix mapping warnings, re‑run affected tests, and create bug tickets for failures—fully functional in demos.
AI-written summary · about
chapters (15)
- 0:00Basil introduction
- 5:22Basil as code quality tool
- 7:34Basil traceability overview
- 15:24Basil API automation
- 27:15Q&A
- 30:06KSNV introduction
- 31:53What KSNV does and why it is needed
- 35:51KSNV reverse engineering
- 42:27Binary versus source analysis
- 44:42KSNV safety analysis
- 46:52KSNV data highlighting
- 48:34KSNV diagrams demo
- 52:33KSNV future features
- 56:32KSNV maintainer reliability Q&A
- 1:00:10Closing Q&A
related talks
39mBASIL an Open Source Software for Quality Management
24mBASIL: Traceability as Code
25mKnowledge Transfer by Source Code
27mContinuous Compliance: Agile Practices for Software Compliance
44mAI Architecture Thinking: From Idea to Impact
27mHow Software Transparency Can Help Save the World
37mDefining and maintaining requirements in the Linux...
30mFast, Lean, Precise, Controlled: Compliance Automation With OSCAL in Our Open-S...