Skip to main content

Welcome to REQQA

REQQA — Requirements Quality Assurance with AI — helps you write better requirements and find the faults in them before they reach a developer. You manage your requirements, user stories, personas, and a shared glossary in one place, and REQQA applies AI-driven analysis — the DeFOSPAM technique — to surface the ambiguities, omissions, and contradictions that requirements always hide.

This page orients a brand-new user. It tells you what a first session looks like, in the order things actually happen, and points you to the deeper how-to and reference pages when you need them.

tip

You don't have to read everything first. The fastest way to understand REQQA is to walk one real requirement from typed to analysed to story. This page is that walk.

What REQQA helps you do​

  • Capture requirements under a clear, structured mission — typed in directly or imported in bulk from a spreadsheet.
  • Analyse each requirement (and each Gherkin story) with AI, getting back a queue of concrete issues classified by the DeFOSPAM technique.
  • Improve requirements iteratively — synthesis and cleanup feed analysis findings back into the wording so the next pass is sharper.
  • Generate user stories and features from requirements, then analyse those too.
  • Share understanding through a glossary of agreed terms that the analysis engine reads.
  • Organise work into releases so you can see what's in and out of a given delivery.

REQQA is multi-tenant: everything you do lives inside an organisation, and everything inside that organisation is grouped into applications. You'll meet both in your first few minutes.

The shape of a first session​

A typical first session moves through six steps. Each builds on the one before it.

1. Get into an organisation​

Every account belongs to an organisation — the tenant that owns your applications, requirements, and AI configuration. REQQA is currently invite-only, so you reach an organisation either by being invited into an existing one or by having one provisioned when your access request is approved. Once you're in, you're ready to create your first application.

2. Open or create an application​

An application is the thing you're specifying — a product, a service, a system. It is the container for all the requirements, stories, and personas that describe it. Your first move is to open an application that's already there, or create a new one.

→ Create your first application walks through this step in full.

3. Write its mission​

This is the step that matters most. The mission statement sits at the top of your requirements hierarchy — every requirement and every story you create sits underneath it and inherits its context. When REQQA analyses a requirement or generates stories, it reads the mission to understand what your application is for. A thin mission gives the AI almost nothing to reason with; a comprehensive one makes everything downstream better.

When you create an application, REQQA pre-fills the mission with an eight-section guideline template — business purpose, scope, stakeholders, operational concept, scenarios, assumptions, constraints, and references. Replace each note with your own content.

→ Writing your application mission explains each section, and Example: a comprehensive mission shows the level of detail to aim for.

caution

It's tempting to skip the mission and jump straight to requirements. Resist that. Time spent here pays back many times over in the quality of what REQQA generates and analyses below it.

4. Add requirements​

With a mission in place, start capturing requirements. You can type them in one at a time against a requirements template, or import a batch from a CSV file if you already have a backlog elsewhere. Requirements are versioned, so REQQA keeps an audit trail of changes as you refine them.

→ How to manage your requirements covers adding, editing, and organising; Importing requirements covers the bulk route.

5. Analyse a requirement​

Now run REQQA's reason for existing. Open a requirement and analyse it: REQQA sends it, together with the mission and any glossary terms, to the AI and returns a queue of issues — each tagged with a DeFOSPAM analyser code so you know what kind of fault it is. Work through the queue, fix the wording, and analyse again. This loop is the heart of using REQQA.

→ Analysing a requirement walks through your first analysis run and how to read the results.

6. Generate stories​

Once a requirement reads cleanly, generate user stories from it. Stories give you testable, Gherkin-shaped detail — and you can analyse stories with the same engine that analyses requirements, so the quality bar carries all the way down.

→ Generating stories shows how.

Where to go next​

If you want to…Go to
Set up your first application step by stepCreate your first application
See the whole app at a glanceA tour of REQQA
Understand the concepts behind the workflowManual: Introduction
Get the mission rightWriting your application mission
Ask a quick questionWhat is REQQA?
note

Throughout the help, Release is the word you'll see in the interface for a unit of delivery; under the hood it's modelled as a scope. You'll meet releases once you're past your first requirements — see Releases and scopes when you're ready.