Mantra – Open-Source Tooling for Requirements Traceability
summary
An open-source CLI tool in Rust manages requirement IDs defined in Markdown or a JSON schema, detects traces in Rust with tree-sitter AST-based tracing and via regex markers for other languages, links tests and statement coverage to those traced lines, and stores results in a mantra.db SQLite after running mantra collect. mantra report emits JSON (fixed schema) or HTML (Tera templates); a pacemaker embedded demo proves the workflow end-to-end.
AI-written summary · about
chapters (12)
- 0:00Mantra introduction
- 1:06Speaker background
- 1:48Why traceability matters
- 2:30Motivation for Mantra
- 3:14Defining requirements
- 4:17Tracing to Rust code
- 5:41Language-specific tracing
- 6:44Linking tests to requirements
- 8:11Manual verification
- 8:31Generating reports
- 9:37Future plans
- 11:45Closing & contributions
related talks
25mContinuous compliance with Rust in automotive software
32mImplementing Requirement Traceability in the Xen FuSa Project with OpenFastTrace
10mAutomatically Enforcing Rust Trait Properties
27mContinuous Compliance: Agile Practices for Software Compliance
06mGraphQL tooling in Rust
29mMacromancy: an introduction to Rust macros
20mOne YAML To Rule Them All: Declarative Config
31mValidating Rust for industry: Certification meets formal analysis