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

Performance Requirements

Specify measurable criteria like response time, throughput, and resource usage under various conditions.

Performance Requirements

What you'll learn: You'll learn how to define concrete, measurable performance criteria that your software must meet.

What Are Performance Requirements?

Performance requirements specify how fast and how efficiently your system must operate. Unlike functional requirements that describe what the system does, performance requirements describe how well it does those things under real-world conditions.

Think of it like specifying a car: functional requirements say "must transport passengers," but performance requirements say "must accelerate 0-60 mph in under 8 seconds" or "must achieve 30+ miles per gallon on highways."

Key Performance Metrics

Response Time

How quickly the system responds to user actions. Example: "Search results must display within 2 seconds for 95% of queries."

Throughput

How many operations the system can handle in a given time period. Example: "The system must process at least 1,000 transactions per minute during peak hours."

Resource Usage

How much memory, CPU, disk, or network the system consumes. Example: "The mobile app must use no more than 100 MB of RAM during normal operation."

Why Measurable Criteria Matter

Vague requirements like "the system should be fast" are impossible to verify. Measurable criteria like "page load time under 3 seconds for 90% of requests" give developers clear targets and testers objective pass/fail conditions.

Always specify:

  • The metric (what you're measuring)
  • The threshold (the acceptable value)
  • The conditions (when this applies: peak load, normal use, specific scenarios)

Key Takeaway: Performance requirements transform subjective expectations like "fast" into objective, testable criteria with specific numbers, conditions, and success thresholds.