Part 1 of 9 · 1 min read
Why this page comes first
In this module you will
- Say what a requirement is, and tell a functional requirement from a non-functional one.
- Ask a short list of questions that pins down what a system must do, for how many users and how fast.
- Turn vague words such as "fast", "many users" and "reliable" into numbers that a design can be checked against.
- Write down assumptions and a list of things the design will not do.
- Explain why asking questions first is a sign of skill and not of weakness.
A design is only good or bad compared with a goal. Without a clear goal, a design is a guess. This page is about getting the goal, before any box is drawn.
The mistake it prevents is common. A designer hears "build a photo app", starts drawing at once, and an hour later has a fine design for the wrong system.