Frequently asked questions

QRA builds the QRA Platform, which analyzes and improves engineering requirements as they are written. QVscribe evaluates each requirement against your standards using deterministic scoring, so the same input under the same configuration produces the same result every time. ReqWriter proposes rewrites that QVscribe scores independently, and the platform keeps a record of what was checked and which configuration was used.

Teams building mission- and safety-critical systems: aerospace and defense, medical devices, automotive, semiconductors, and energy are the most common.

No. Your requirements stay where they live today. The QRA Platform analyzes the quality of the requirements themselves, scoring each one, identifying the specific words and patterns behind the findings, and keeping a record of what was checked, alongside the tools that manage them.

QVscribe is the requirements evaluation engine of the QRA Platform. It scores engineering requirements for clarity, consistency, and quality in Microsoft Word and Excel through a task-pane add-in, inside IBM DOORS Next, Siemens Polarion, and Jama Connect through a browser extension, and in the web interface.

QVscribe evaluates requirements deterministically: the same requirement, under the same configuration, receives the same score and findings every time. Every 1-to-5 score is built from named Problem Types. Each finding identifies the rule that triggered it and the exact words involved, so engineers can see why a requirement scored the way it did and what to fix.

Four kinds. Quality analysis scores each requirement from 1 to 5 against named Problem Types grounded in INCOSE guidance, with the triggering words highlighted. Conformance checking covers EARS down to the individual templates. Consistency checking holds terminology and units to your configured glossary. Similarity analysis surfaces near-duplicate requirements across the set.

Anyone whose decisions depend on requirements quality: authors applying their team’s rules while writing, reviewers who need consistent criteria and a retained result, teams evaluating incoming specifications before committing to delivery, engineering leaders tracking where quality issues concentrate, and test engineers identifying requirements that are difficult to verify before test planning begins.

Yes. Configurations are named and versioned, and carry your rules, approved glossary terms, units, and required level of strictness, using the built-in levels or your own customized versions. Requirements are evaluated against your organization’s standards rather than a fixed rubric.

Yes. QVscribe analyzes whole documents and requirement sets in one pass. It scores each requirement and checks for similarities across the set.

Microsoft Word and Excel through a task-pane add-in; IBM DOORS Next, Siemens Polarion, and Jama Connect through a Chrome and Edge browser extension; and the web interface.

Teams using other requirements management systems can often analyze their requirements through Word or Excel. Book a call and we will look at your setup together.

Not directly. Open the PDF in Microsoft Word or Excel and analyze it there.

The web interface and the Chrome and Edge browser extension run on macOS. For the Word and Excel add-in in your specific environment, book a call and we will confirm the fit.

System requirements are kept up to date in the product documentation and release notes. Contact us for guidance on your specific environment.

Sync with supported requirements systems is read-only and never writes back to the source system. The browser extension uses the engineer’s existing session and permissions, so there are no separate service accounts.

No. ReqWriter uses AI to propose rewrites of existing engineering requirements. The engineer decides what stays, and authorship of the requirement remains theirs.

ReqWriter supports document-level workflows with review and acceptance at the individual requirement level. When QVscribe analyzes a document, ReqWriter generates rewrites for the analyzed requirements. In Word and Excel, a rewrite is available from the flagged requirement’s dropdown; in your requirements platform, select a requirement to view its suggestion. An engineer reviews and decides whether to accept each rewrite.

Yes. ReqWriter uses your configuration, including your rules, approved glossary terms, and units, to guide rewrites. This helps suggestions reflect your organization’s terminology and requirements standards rather than relying on generic English.

ReqWriter uses generative AI, so suggested rewrites can vary between runs. If a draft doesn’t suit your needs, you can generate another. What remains consistent is the evaluation: QVscribe scores each draft against the same configuration, so engineers can check whether the identified problem has been addressed.

QVscribe evaluates every rewrite suggestion independently before an engineer accepts it. The system that generates the rewrite is separate from the system that grades it, and the engineer decides whether to apply the change.

Yes. Every result carries the requirement text, score, findings, and the configuration and engine versions behind it. Snapshots capture the scored state of a document, and timelines show how requirements quality changed between project gates, giving teams a record for design reviews and audits.

Configurations are named, versioned, and shared across teams and projects. Organizations can designate internal configuration authors who are responsible for maintaining and updating configurations, defining the standards each one applies, and establishing when to use each version. Our Customer Success team provides training to help configuration authors manage updates and establish a process that works for their organization. The record shows which configuration version was used for each result.

QRA follows security practices informed by the OWASP Top 10 and is working toward ISO 27001 certification. Sync with supported requirements systems is read-only and uses the engineer’s existing permissions. Deployment and security details depend on your environment, and your security reviewer is welcome to join a demo.

Book a call and bring a requirement you already know is weak. You’ll see it scored, rewritten, and re-scored on the spot.