Skip to content

Stockertim Dictionary · Project management

Functional requirement

Also called functional requirements

In short

A statement of something a solution must do, such as record a payment or send a confirmation, that can be demonstrated and tested.

  • Beginner
  • Concept
  • Checked

In detail

A functional requirement describes a behaviour of the solution: an action it performs, information it records, a calculation it makes or a rule it applies. Examples are "the system records the date and amount of every payment" or "a customer receives an email confirmation within five minutes of booking". Each can be shown to work or not work.

Good functional requirements are clear, testable, necessary and free of design detail. They say what is needed, not how it should be built, which leaves designers free to find the best way. Each should trace back to a business need, have an owner and a priority, and come with acceptance criteria that define when it has been met.

Functional requirements are only half the picture. A system can do everything on its list and still fail if it is too slow, insecure or hard to use. Those qualities are captured as non-functional requirements and need the same care. In adaptive projects, functional needs are often written as user stories rather than formal statements.

In practice

Requirement registers list each functional requirement with an identifier, priority, source and acceptance test; testers build test cases directly from them.

Watch out

  • A requirement that cannot be tested cannot be accepted.
  • Writing the solution into the requirement, such as using a drop-down menu, limits better designs.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English