Requirements

The Requirements page lets you define, organize, and trace engineering requirements across your program. Requirements live in tables that you can customize with columns, groups, and filters.

​

Tables

Each program can have multiple requirement tables — for example, one for system-level requirements, another for test cases, and another for customer needs. Create a table from the Requirements page, then add columns to define the data you want to track for each requirement.

​

Creating requirements

Each requirement has core fields:

• Number — Auto-generated or custom identifier
• Name — Short title
• Statement — Full requirement text
• Type — Functional, performance, interface, constraint, user need, or test case
• Status — Draft, review, approved, rejected, or deprecated
• Owner — Assigned team member

You can also create parent-child relationships between requirements to build a hierarchy.

​

Custom columns

Add columns to your tables to track additional data. Columns support the same types as node attributes — text, number, date, select, and more. Reorder columns by dragging their headers.

​

Filtering and grouping

Use the toolbar to filter requirements by status, type, owner, or any custom column. Group rows by a column value to organize large tables — for example, group by status to see all approved requirements together.

​

Traceability links

Link requirements to other requirements, to nodes in your system architecture, or to artifacts. These links create a traceability web that you can visualize in the graph view. The graph view shows how requirements connect to nodes and artifacts, helping you verify coverage and identify gaps.

​

Importing requirements

Import requirements from Excel or CSV files: