A functional requirement describes a behavior: something the solution does in response to an input or an event. "When a return is scanned, the system shall show the refund amount." You can usually test it with one scenario.
A non-functional requirement (also called a quality attribute) describes how well the solution must work, across many functions. The common categories:
- Performance: how fast, how many at once. "Search returns results within 2 seconds for 500 users."
- Availability: when it must be up. "Available 7:00 to 23:00 every day, 99.5% of that time."
- Security: who can do what, how data is protected.
- Usability and accessibility: how easy, for whom. "Meets WCAG 2.2 AA."
- Compliance: laws and standards it must follow.
Non-functional requirements are the ones most often forgotten, and the ones that cause the most expensive rework. Every one needs a number or a standard, or it cannot be tested.