Course contentsShow
← Software Engineering
Lesson 124 of 1,9334. Requirements EngineeringFree lesson

Functional vs Non-Functional Requirements

Learn the fundamental distinction between what the system does and how well it performs those functions.

Functional vs Non-Functional Requirements

What you'll learn: You'll understand the crucial difference between what a system does and how well it does it.

The Core Distinction

When gathering requirements for software, you're answering two fundamentally different questions:

Functional requirements describe what the system should do—the specific behaviors, features, and functions users need. These are the actions and capabilities that deliver business value.

Non-functional requirements describe how well the system should perform those functions—the quality attributes like speed, security, reliability, and usability that make the system acceptable to use.

Understanding Through Examples

Think of a car:

  • Functional: "The car must accelerate when the driver presses the gas pedal" or "The car must stop when the brake is applied"
  • Non-functional: "The car must accelerate from 0-60 mph in under 8 seconds" or "The braking system must remain effective in wet conditions"

For a login system:

  • Functional: "Users must be able to log in with email and password"
  • Non-functional: "The login process must complete within 2 seconds" and "User passwords must be encrypted using industry-standard algorithms"

Why Both Matter

Functional requirements tell developers what to build. Non-functional requirements tell them how good it needs to be. You can build a login system that technically works but is so slow, insecure, or confusing that nobody wants to use it.

Both types work together: functional requirements define the system's capabilities, while non-functional requirements constrain and shape how those capabilities are implemented.

Key Takeaway: Functional requirements define what your system does; non-functional requirements define how well it does it. Both are essential for building software that truly meets user needs.