Skip to main content
PProfileMatch
← Path

System Design · System Design Basics: How to Approach Any Design Problem

0 XP
  1. 1 current stop: learning
  2. 2 upcoming
  3. 3 upcoming
  4. 4 upcoming
  5. 5 upcoming

Finish after stop 5

Stop 1 of 5 · Map room at the start of the trail

Trick to keep in mind+3 XP

Features are the menu; non-functional requirements are how fast and how hot it arrives.

A functional requirement names something the system does: upload, follow, comment. A non-functional requirement describes a quality of that behaviour: how quickly it responds, how often it is up, how much load it takes, how fresh the data is. A useful test is whether you can measure it with a number or a percentage rather than ticking it off as present or absent.

Read it once, then a question tests whether the trick stuck.