Behavior

Functional Analysis

Turns a requirements document into functions, a functional flow, an FFBD and the tables that go with them.

Where to find it

In the navigation rail: Behavior → Functional Analysis.
In a document: More ▾ → Functional Analysis (functions, FFBD, tables)….
Address options: functional?doc=<id> and &tab=functions|flow|tables|coverage.

View bar: the scope (all requirements or one document) and the top-level function (Choose…). Top bar: Assignment Report (DOCX) and Open FFBD. ✦ AI ▾: Extract Functions with AI… and Suggest Flow with AI….
Functions: Rule-Based Extraction… makes one function per functional requirement (using the Functional and Performance Requirement labels, or the outline when there are none). The editable preview renames, merges, splits, reassigns requirements, sets parents and reorders (F1…Fn). Apply creates the Actions and satisfied by links as one undo step.
Flow & FFBD: Wrap in AND / OR / LOOP, Unwrap, + Branch, drag to reorder, or Edit as Text… with a compact notation such as AND(F6 | F8) -> F4 -> LOOP[F1, return="next sortie"](F5 -> F2). A loop can be a function (drawn with a dashed frame). The FFBD card sets start, end and orientation.
Tables: the requirements table (No., Name, Requirement, Type, Score) and the functions table (ID, Function, Requirements, optional Subsystem), each with Copy, CSV, XLSX and DOCX and an editable caption.
Coverage: requirements not allocated to any function and functions with no requirement.

Running the extraction again updates the existing functions (matched by their links, then by name) and keeps their names; the Status column shows number changes, and Rename opts in to a proposed name.
The flow is the same data the Action Diagram, FFBD and Simulator use.