DEV Community

Joud Awad
Joud Awad

Posted on

Functional Requirements in System Design Interviews: 5-Step Method

Functional requirements decide what your system design must do. Each one should trace back to a screen the user sees.

A requirement you can't trace is a guess. It wastes your time or breaks the design later.

Here's the 5-step method:

  1. Sketch the screens: draw what each user sees, including the ones nobody remembers, like the driver's app.

  2. Pull the actions: list every button and form on those screens. Each action is a candidate requirement.

  3. Chain the user journeys: put the actions in order, and add a system lane for the steps no screen shows, like assigning a driver.

  4. Write the requirement lines: one action per line, phrased so the answer is yes or no. "A customer can cancel an order before pickup."

  5. Scope them: sort every line into core, nice-to-have, or out of scope, then say that scope out loud.

In short: start from what users see, not from boxes or a feature list you remember.

Full animated breakdown on my YouTube channel, System Design Lab. It runs the method on food delivery, Twitter, a one-line work ticket and a URL shortener:
https://youtu.be/2M-toJuKlYY

Over to you: in a Twitter design, are likes a core requirement or a nice-to-have, and why?

Top comments (0)