Getting Started

Go from zero to your first baselined requirement in under ten minutes. This guide walks you through every step.

1. Create Your Account

Head to airgen.studio and click Get Started. Fill in your name, email address, and a password. You will receive a verification email within a few seconds — click the link inside to activate your account.

If you are joining an existing team, ask your administrator to send you an invitation link instead. Accepting the invite will add you to your team's tenant automatically.

2. Set Up Your Workspace

After you sign in for the first time, AIRGen creates a default workspace (tenant) for you. A workspace is the top-level container that holds all of your projects, users, and settings.

To create your first project, open the Dashboard and click New Project. Give it a name and an optional description. Projects contain requirements, documents, architecture diagrams, linksets, and baselines — everything lives inside a project.

3. Upload a Document

Navigate to Documents in the left-hand sidebar. Create a folder to keep things organized, then click Upload. AIRGen accepts Word (.docx) and PDF files.

Once uploaded, AIRGen parses the document into a hierarchical tree of sections automatically. Each section becomes a first-class node in the project graph, ready to be linked to requirements, architecture blocks, and other sections.

4. Create Your First Requirement

Go to Requirements and click Add Requirement. You can write the requirement text manually using the inline editor.

Alternatively, open AIRGen's AI Chat panel and describe what you need in plain language — for example, "The braking system shall respond within 150 ms of pedal input." AIRGen generates 1-5 compliant requirement candidates. Review each candidate, edit as needed, and click Accept to add it to your project.

5. Run QA Scoring

Select one or more requirements in the list and click Run QA Scorer. AIRGen's background worker evaluates each requirement against a set of deterministic quality checks based on ISO/IEC/IEEE 29148.

Every requirement receives an overall score plus individual rule results. Common checks include: unambiguous language, measurability, feasibility, singular responsibility, and correct use of "shall" vs. "should". Fix any flagged issues and re-score to confirm improvements.

6. Create Trace Links

Go to Links and click Create Linkset. A linkset defines a category of trace relationships — for example, "Requirements to Document Sections" or "System to Subsystem Requirements".

Inside the linkset, add individual links by selecting a source node and a target node. You can link requirements to document sections, architecture blocks, or other requirements. All links are stored in AIRGen's Neo4j graph and can be navigated visually or queried programmatically.

7. Take a Baseline

Go to Baselines and click Create Baseline. A baseline is a point-in-time snapshot of your entire project state — every requirement, document, link, and architecture block at that moment.

Name the baseline with a version identifier (e.g., "v1.0-draft") and add an optional description. After creation, you can compare any two baselines side-by-side to see exactly what was added, changed, or removed between releases. Baselines serve as your official release evidence and audit trail.

8. Next Steps

You now have a working project with a document, requirements, QA scores, trace links, and a baseline. Here is where to go next:

• Requirements Management Guide — Deep dive into requirement editing, versioning, filtering, and bulk operations.
• Architecture Diagrams Guide — Build visual block diagrams, define interfaces, and link components to requirements.
• Administration Guide — Configure users, roles, RBAC policies, and tenant-level settings.