# Functional Requirement

A requirement describing a capability or behavior a product must provide in response to defined conditions.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/functional-requirement/>)

## What it means

A functional requirement specifies an observable action, rule, or response the product must support. It describes what the system does, including inputs, outputs, and business rules, rather than qualities such as speed, availability, or accessibility, which are non-functional requirements.

## Why it matters

The distinction helps teams make behavior testable without hiding quality constraints that also determine whether the product is usable and safe.

## When to use it

Use functional requirements for behavior that needs precise agreement or verification. Pair them with relevant non-functional requirements instead of treating behavior as sufficient on its own.

## How it works

1. Name the actor and triggering context.
2. Describe the required behavior and result.
3. Specify important rules and exceptions.
4. Define observable verification examples.
5. Check interactions with quality and compliance constraints.

## A practical example

When a customer schedules a transfer, the banking service must show the final amount, date, and fees before confirmation and must create only one transfer after a repeated submission.

## Where it breaks

Functional requirements do not establish desirability, usability, performance, security, or business value; exhaustive lists can also constrain better solutions.

## Common mistakes

- Calling every requirement functional.
- Leaving error and boundary behavior unspecified.
- Assuming passing functional tests proves product quality.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/functional-requirement/#visualization-functional-requirement>)

## Sources

1. [ISO/IEC/IEEE 29148:2018](<https://www.iso.org/standard/72089.html>) — ISO · International standard
2. [Agile Workflow in Azure Boards](<https://learn.microsoft.com/en-us/azure/devops/boards/work-items/guidance/agile-process-workflow?view=azure-devops>) — Microsoft Learn · Official product documentation

## Related topics

- [Product Requirement](<https://wiki.soroush.uk/topic/product-requirement/>)
- [Non-Functional Requirements](<https://wiki.soroush.uk/topic/non-functional-requirements/>)
- [Acceptance Criteria](<https://wiki.soroush.uk/topic/acceptance-criteria/>)
