Functional Requirements
A behaviour the system must gain or change: what it does in response to a user or event. Behaviour it already has is described in FDR design records.
About functional requirements
A behaviour the system must gain or change: what it does in response to a user or event. Behaviour it already has is described in FDR design records.
Example: "Dropping a card on another column changes the customer's status."
Records say what should change and belong to an initiative; the initiative chosen in the context row below the top bar filters this list (Show all of the solution lifts it). What the solution already is lives in its design records under Design.
What you can do here
- Search by title, code or statement, and filter by state. Press Apply to run the filter.
- Switch between List (a table) and Cards (statements visible at a glance).
- The Acceptance column shows how many acceptance criteria are verified as met. No criteria marks a requirement that still needs them.
- Open a record to read or edit it, or add one with New record.
Tip Filter by Retired to see records that no longer apply; they are hidden in Explorer.