Part 2 of 7 · 1 min read
Questions before classes
A vague prompt hides the real requirements.
A customer who orders "a cake" has not told the baker the size, the flavour or the day. A good baker asks. A good candidate does the same, because a one-line prompt hides most of the requirements.
Questions fall into four groups (common practice):
| Group | Examples for a meeting room system |
|---|---|
| Who uses it | Staff only, or visitors too? Is there an admin? |
| What can they do | Book, cancel, change, search for a free room? |
| What are the limits | Longest booking? Booking how far ahead? Repeats? |
| What counts as failure | Double booking, a room closed for repair, a past time |
Write each answer on the board. These are the functional requirements: what the system does. Qualities such as "must handle two people booking at the same moment" are non-functional, and in LLD they often show up as concurrency or validation rules.
Functional requirement
A functional requirement states something the system must do, in a sentence a user could check.
Example: "A user can cancel a booking they made, and the room becomes free again."
Check yourself: 1. Which question group does "can visitors book?" belong to? 2. What is a non-functional requirement for the room system? 3. Why write answers on the board?