ReqView review: Git-based requirements management for regulated industries, with ISO/FMEA templates, traceability, and Jira/DOORS integrations. See pricing,…
ReqView is a requirements management tool built for hardware, software, and systems engineering teams in regulated industries such as medical devices, aerospace and defense, automotive, and railways. It lets teams capture requirements in Word documents or ISO/IEC/IEEE 29148:2018-based templates (and FMEA templates), then manage them in structured, tabular documents with custom attributes, filtering, and comparison views. Requirements are stored in Git or Subversion in a human-readable JSON format, giving teams version history, branching, and merge/diff support without a proprietary database. ReqView's core strength is end-to-end traceability: it links requirements to verification, validation, and risk items and generates multi-level traceability and impact-analysis reports so teams can see what breaks when a requirement changes. Documents can be exported to Word, Excel, PDF, and HTML for audits and formal specifications. It integrates with Jira and Azure DevOps for agile workflows, Sparx Systems Enterprise Architect for MBSE, and other requirements tools such as IBM DOORS via the ReqIF exchange format. ReqView is developed by Eccam s.r.o., based in Prague, Czech Republic, and has been on the market since 2013, reporting over 26,000 users across 150+ countries.
Key Features
Word & template import — Import requirements from Word documents or start from ISO/IEC/IEEE 29148:2018 and FMEA specification templates.
AI-assisted PDF import — Extract requirements automatically from existing PDF documents using AI-assisted import.
Git & Subversion storage — Requirements are stored as human-readable JSON in Git or Subversion, giving full version history, branching, and diff/merge support.
End-to-end traceability & impact analysis — Link requirements to verification, validation, and risk items, and generate multi-level traceability and impact-analysis reports.
Export to Word, Excel, PDF, HTML — Generate customizable requirement specification documents and reports in Word, Excel, PDF, and HTML formats.
Jira, Azure DevOps, Sparx EA, ReqIF — Integrates with Jira and Azure DevOps for agile workflows, Sparx Systems Enterprise Architect for MBSE, and exchanges data with tools like IBM DOORS via ReqIF.
Dashboards & table views — Team and Enterprise plans add dashboards, configurable table views, export configurations, and linked projects for team collaboration.
Pros & Cons
Pros
Requirements stored as human-readable JSON in Git or Subversion, giving full version history, branching, and diff/merge without a proprietary database
Built-in ISO/IEC/IEEE 29148 and FMEA templates speed up compliance work in regulated industries
Strong end-to-end traceability and impact-analysis reporting across requirements, verification, and risk items
Integrates with Jira, Azure DevOps, and Sparx Enterprise Architect, plus ReqIF exchange with tools like IBM DOORS
Free plan and a 14-day full-featured trial let teams evaluate before committing to a paid seat
Cons
Per-user annual pricing (from €440/year) is billed yearly, not monthly, which is a larger upfront commitment for small teams
The FREE plan is read-only and capped at one document and 150 objects, so it's only useful for evaluation, not real work
Git/SVN-based version control has a learning curve for requirements teams unfamiliar with source-control workflows
Enterprise floating-license pricing (from €5,400/year for 3 clients) targets larger organizations, making it less accessible for solo users