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

Reliability and Availability Requirements

Establish expectations for uptime, fault tolerance, and system behavior during failures.

Reliability and Availability Requirements

You'll learn: How to define when and how reliably your system must be operational for users.

What Are Reliability and Availability Requirements?

Reliability specifies how consistently your system performs correctly over time, while availability defines how accessible the system must be. These are two related but distinct non-functional requirements that set clear expectations for uptime, fault tolerance, and system behavior when things go wrong.

Think of it like a local fire station: availability means the station is open and staffed 24/7, while reliability means when you call 911, the equipment works, trucks start, and firefighters actually arrive. A system can be available (turned on) but unreliable (constantly failing).

Core Concepts

Availability is typically measured as a percentage of uptime:

  • 99% availability = ~3.65 days downtime per year
  • 99.9% ("three nines") = ~8.76 hours downtime per year
  • 99.99% ("four nines") = ~52 minutes downtime per year
  • 99.999% ("five nines") = ~5.26 minutes downtime per year

Reliability focuses on correct operation without failures:

  • Mean Time Between Failures (MTBF): How long the system runs before failing
  • Mean Time To Recovery (MTTR): How quickly you restore service after failure
  • Error rates: Acceptable failure percentage for transactions

Fault tolerance requirements define how the system handles failures—does it degrade gracefully, fail safely, or maintain full operation with redundant components?

Examples

  • "The payment service must maintain 99.95% availability during business hours"
  • "Data writes must succeed with 99.999% reliability"
  • "System must automatically recover from single server failures within 30 seconds"

Key Takeaway: Reliability and availability requirements quantify your system's uptime expectations and acceptable failure behavior—essential for setting realistic service level agreements and architectural decisions.