/ 01. Req.Gen^
Req.Gen^
Every production system starts from requirements. Now they write themselves.
From high-level intent — or from legacy / PoC code — Req.Gen^ produces a fully decomposed, traceable requirements baseline at product, system and component level. The old Rev.Eng workflow is built in: start clean or start from what you've already got.
Two ways in
Greenfield or brownfield.
/ Mode A · Greenfield
From specs.
Drop in requirements docs, regulations, design standards, customer specs. Req.Gen^ decomposes them into systems, components and traceable item-level requirements.
— accepts: .docx · .pdf · ReqIF · JSON · XML · and more…
/ Mode B · Brownfield
From legacy code.
Inherited a PoC, a research script, or production firmware with no spec? Req.Gen^ reverse-engineers it into a clean, structured baseline you can take forward.
— accepts: C/C++ · Rust · Python · Simulink · LD · ST
Decomposition tree
From product intent to every requirement.
Every requirement traces back to its node — and forward to its standard and test ↓
What you get
- Output format
- ReqIF · XML · JSON · CSV
- Traceability
- Bidirectional — req ⇄ source, req ⇄ test, req ⇄ standard
- Human review
- Inline approval workflow.
- Hand-off
- Direct hand-off to Test.Auth^ — or export and stop here
Next stage →
Test.Auth^
Test.Auth^ turns these requirements into executable verification.