Part 2 of 9 · 1 min read
A requirement is a promise to the user
What a requirement is, and why a design cannot start without them.
Think of ordering a cake. The baker asks: how many people, which flavour, any allergies, what day? Each answer narrows the cake. Without the answers, the baker could make a beautiful cake that nobody can eat.
A system has the same need. Each answer about what the system must do is a requirement.
Requirement
A requirement is a statement of something the system must do, or a quality it must have, written clearly enough that a person can check whether the finished system meets it.
Example: "A customer can place an order and sees a confirmation within two seconds."
Requirements come in two kinds. The kinds are asked about in different ways, and a design is shaped by both.
Functional requirement
A functional requirement says what the system does: a feature, an action, a result.
Example: "A user can upload a photo." "A user can see the photos of the people they follow."
Non-functional requirement
A non-functional requirement says how well the system must do it: how fast, how many users, how reliable, how secure, how costly.
Example: "Photos appear within one second for 99 out of 100 views." "The service is up at least 99.9 percent of the time."
Both kinds matter, but they push the design in different directions. The first kind decides which parts are needed. The second kind decides how big and how strong those parts must be.
Check yourself:
- Is "users can reset their password by email" functional or non-functional?
- Is "the home page loads in under two seconds" functional or non-functional?