Skip to content

Functional Requirements

Updated 06 Sep 2026

•
def
- •
  statements of services the system should provide, how it should react to particular inputs, and how it should behave in particular situations
- •
  may also state what the system should not do
•
characteristics
- •
  describe functionality or system services
- •
  depend on the type of software, expected users, and type of system
- •
  user-level functional requirements may be high-level statements
- •
  system-level functional requirements should describe services in detail
•
examples
- •
  users can log in using email and password
- •
  the system must send an email notification after a user places an order
- •
  the system must allow users to add tasks to a project
- •
  the system must allow users to print monthly sales reports in PDF format
•
imprecision problem
- •
  ambiguous functional requirements may be interpreted differently by developers and users
- •
  e.g., the term "search" could mean search within one clinic or across all clinics
•
related
•
Cards
- •
  Distinguish functional from non-functional requirements.
  - •
    functional: what the system should do; non-functional: constraints on how it does it (performance, security, usability, etc.)

Linked references 4

◌ Explore connections in Graph view