Requirements Management

Create, score, edit, and manage requirements with AI assistance and deterministic quality checks.

Creating Requirements

You can create requirements manually from the Requirements page in your project.

Click Add Requirement in the toolbar. A new row appears in the requirements table with editable fields. Fill in the following:

• Title — A short, descriptive name for the requirement.
• Description — The full requirement statement. Use precise, unambiguous language with measurable criteria where possible.
• Rationale — Why this requirement exists. Link it to a business need, safety goal, or regulatory mandate.
• Verification Method — How the requirement will be verified: inspection, analysis, demonstration, or test.

To edit an existing requirement, double-click any field in the table to open the inline editor. Changes are saved automatically when you click away or press Enter.

AI-Assisted Generation

AIRGen can generate requirement candidates from natural-language descriptions. This is especially useful when translating stakeholder needs, safety goals, or high-level objectives into formal requirements.

To generate requirements with AI:

1. Open the AIRGen Chat panel from the right-hand side of the Requirements page.
2. Describe your need in natural language. For example: "The infotainment system shall boot to the home screen within 3 seconds of ignition on."
3. AIRGen analyses your project context — existing requirements, documents, and architecture — and generates 1 to 5 candidate requirements.
4. Review each candidate. Click Edit to refine the wording, or click Accept to add it directly to your project.
5. Click Reject to discard any candidate that does not meet your needs.

QA Scoring

AIRGen includes a deterministic quality assurance scorer that evaluates requirements against ISO/IEC/IEEE 29148 quality rules. Unlike AI-based checks, these rules are repeatable, auditable, and produce the same result every time.

To score requirements:

1. Select one or more requirements using the checkboxes in the requirements table.
2. Click Run QA Scorer in the toolbar.
3. The scorer runs as a background worker. A progress indicator shows real-time status as each requirement is evaluated.
4. When scoring completes, each requirement displays an overall score and individual rule results.

The scorer checks the following quality attributes:

• Atomic — The requirement addresses a single concern. It does not combine multiple behaviours or constraints into one statement.
• Unambiguous — The language is clear and cannot be interpreted in more than one way. Vague terms like "fast", "user-friendly", or "adequate" are flagged.
• Verifiable — The requirement includes measurable criteria that can be objectively tested or inspected.
• Traceable — The requirement can be linked back to a source (document, stakeholder need, or higher-level requirement) and forward to verification evidence.
• Consistent — The requirement does not conflict with other requirements in the project.
• Feasible — The requirement is technically achievable within the constraints of the system.

Custom Attributes

Every project has different metadata needs. AIRGen lets you define project-specific attributes that appear as additional columns in the requirements table.

Navigate to Requirements Schema in your project settings. Click Add Attribute and configure:

• Attribute name — The column header displayed in the table (e.g., "Priority", "Status", "Category").
• Data type — Text, number, date, or dropdown (enumerated list).
• Default value — Optional. Pre-fills the field for new requirements.

Common custom attributes include:

• Priority — High, Medium, Low.
• Status — Draft, Under Review, Approved, Rejected.
• Category — Functional, Performance, Safety, Interface.
• Source — The originating document, stakeholder, or standard.
• Verification Method — Inspection, Analysis, Demonstration, Test.

Once defined, custom attributes appear as editable columns in the requirements table and are included in exports and baseline snapshots.

Version History

AIRGen tracks the complete history of every requirement. Each time you edit a requirement's text, rationale, or any attribute, a new version is created automatically.

To view version history:

1. Click on a requirement to open its detail panel.
2. Select the History tab.
3. Browse the list of versions, ordered from most recent to oldest. Each entry shows the date, the user who made the change, and a summary of what changed.
4. Click Compare on any two versions to see a side-by-side diff with additions highlighted in green and deletions highlighted in red.
5. Click Restore on any previous version to revert the requirement to that state. Restoring creates a new version rather than overwriting history.

Archive & Duplicate Detection

Over the course of a project, some requirements become obsolete or redundant. AIRGen provides two features to keep your requirements set clean without losing data.

Archiving

Select one or more requirements and click Archive. Archived requirements are hidden from the default table view but are not deleted. They remain in the project graph and are included in baseline snapshots taken before the archive action.

To view archived requirements, toggle the Show Archived filter in the table toolbar. You can restore an archived requirement at any time by selecting it and clicking Restore.

Duplicate Detection

AIRGen automatically scans for potential duplicates based on text similarity. When the system detects two or more requirements with highly similar descriptions, a notification appears in the requirements toolbar.

Click the notification to review the flagged pairs. For each pair, you can:

• Merge — Combine the two requirements into one, preserving trace links from both.
• Dismiss — Mark the pair as intentionally distinct. The system will not flag them again.
• Archive one — Keep the preferred version and archive the duplicate.