ReqM v3
9-module AI requirements engine — from Business Need to a fully traced, tested SRS. Accepts text, documents, images, and voice.
Why ReqM v3 Exists
Legacy tools like IBM DOORS and Polarion store requirements — they don't generate them, check their quality, or catch gaps before an assessor does. ReqM v3 actively builds a complete Software Requirements Specification through 9 integrated modules, enforcing EARS syntax and IREB CPRE quality criteria automatically, with full bidirectional traceability from business goal to test case.
The ReqM v3 Method
From problem statement
to production-ready SRS.
ReqM v3 guides you through 9 integrated modules in sequence — each building on the last, each quality-gated before you proceed.
Business Need
Enterprise analysis using PESTLE, Five Whys root cause, SMART goals, and change strategy. Generates a gap-driven elicitation plan.
Analysis & Design
Stakeholders → Solution Description → Compliance Identification → Integrations. Every module accepts text, document, image or voice.
Requirements & SRS
EARS requirements → Test cases → End-to-end traceability → Fully assembled SRS exported as ReqIF, CSV, or Word.
The 9 Modules
Capture the actual business problem this system needs to solve, before any solution detail is discussed.
Identify everyone with a stake in the outcome, and what each of them actually needs from the system.
Describe the proposed solution at a level concrete enough to derive real requirements from.
Apply the relevant industry overlay — ISO 26262, IEC 62304, DO-178C, DORA, EU AI Act, or one of 22 total configurations — if your project needs one. Optional; the other 8 modules work identically with no overlay applied.
Define how this system connects to everything around it — other systems, APIs, data sources.
The core module: individual requirements, written and enforced to EARS patterns, scored against IREB CPRE criteria.
Generate test cases directly from requirements — if a requirement can't produce a test case, that's flagged as a verifiability problem back in M6.
Full bidirectional traceability: Business Goal → Stakeholder → Feature → Requirement → Test Case, so any change's impact can be traced in either direction.
Everything from M1–M8 assembled into one complete, exportable Software Requirements Specification document.
22 Industry Overlays, 22 Diagnostic Checks
M4's compliance overlays cover 22 industry configurations — automotive, medical device, aerospace, rail, banking, and 17 more — each pre-loading the relevant standards, terminology, and safety obligations. Separately, 22 diagnostic checks run across the whole SRS: EARS enforcement, orphan requirement detection (a requirement with no trace to any business goal), and change-impact analysis, regardless of whether any industry overlay is active. See the full industries list →
What You Get
- 9 integrated modules — Business Need through SRS Assembly
- 4 input modalities — text, document, image, voice
- 22 industry overlays — ISO 26262, IEC 62304, DO-178C, DORA, EU AI Act, and more
- 22 diagnostic checks — EARS enforcement, orphan detection, impact analysis
- End-to-end traceability — Business Goal → Stakeholder → Feature → Requirement → Test Case
- Export: ReqIF, CSV, JSON — imports into DOORS, Codebeamer, Polarion
Pricing
Free
$0
Modules 1–3, 1 project, 25 requirements, text input only. Permanent, no card.
Professional
$49/mo
All 9 modules unlocked, higher limits.
Team
$129/mo
Multiple seats, shared projects.
Enterprise
$2,500/mo
Custom overlays, dedicated support, SSO.
Compare to IBM DOORS Next at $9,840+/user/year (~$820/user/month).
Frequently Asked
Start with Modules 1–3, free
1 project, 25 requirements, no card required.
Open ReqM v3 → Explore Requirement Analyser → Explore ReqCompass →