Exploring possibilities for integrating StrictDoc with ELISA's requirements temp...
summary
A working GitHub repo demonstrates StrictDoc parsing Linux source and sidecar files, merging nodes, running custom validations (example: requirement has test), and exporting linked requirements/design/tests as HTML; CI shows the automation steps and diff views for maintainers. Most ELISA needs map directly (SPDX-REQ- parsing supported). Remaining gap is drift detection: StrictDoc records proximal code and metadata but lacks built-in hash-based drift detection* (current stable ID generation needs aligning and semantic hashing is suggested).
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 1:30Demo repository and automation
- 2:31Introduction to StrictDoc
- 4:23Linux integration workflow
- 6:36Adding new requirements
- 11:45Extending traceability model
- 13:12Vendor requirements and traceability
related talks
27mContinuous Compliance: Agile Practices for Software Compliance
47mEngineering Documentation
24mEscaping the Curse of Outdated Docs
41mCross Industry Demands and Collaboration Opportunities
05m“Validating Lemmas with Rustdoc [...]”
53mDocumenting the Design of the Linux Kernel
47mDocumentation as code (explained to my dad)
35mThe practical implementation of Documentation as Code