Part 3 of 7 · 1 min read
A worked requirements list
Turn the answers into numbered rules.
After the questions, the interviewer's answers become a short list. A made-up one for the room system:
- There are many rooms. Each has an id, a capacity and a floor.
- A user books one room for a time slot on one day. Slots are whole 30-minute blocks.
- Two active bookings for the same room must not overlap.
- A user can cancel their own booking. A cancelled booking frees the room.
- A user can search for rooms that are free for a slot and large enough for a number of people.
- Out of scope: payments, repeating bookings, equipment, several buildings, notifications.
Numbering helps. Later, each class and method can point back to a requirement, and the interviewer can see nothing was forgotten.
The size of the problem also gives hints. Made-up numbers: 50 rooms, 8 working hours a day, 30-minute blocks. That is 16 blocks per room per day, so 50 × 16 = 800 blocks a day. This is small enough to keep in memory, so no database design is needed. Saying so out loud shows judgment.
Check yourself: 1. Which numbered requirement is the central rule? 2. How many blocks does one room have in a day? 3. Why is "out of scope" part of the list?