CSE Roadmap

Core tier · about 4 hours · 6 parts

Part 2 of 6 · 1 min read

Requirements

Ask, then write numbered rules.

Think of a car park attendant. Before taking the job, the attendant would ask how many floors there are, which vehicles come, and how the fee works. A design round starts the same way.

Questions to ask, with the answers assumed here:

  1. Which vehicles come? Bikes, cars and trucks.
  2. Which spots exist? Small, medium and large, on several floors.
  3. Which vehicle fits where? A bike fits any spot, a car fits medium or large, a truck fits large only.
  4. How is a spot chosen? The smallest spot type that fits, so large spots stay free for trucks.
  5. How is the fee set? Per started hour, with a different rate for each vehicle type.
  6. Is the lot used by many gates at once? Yes, so the lot must be thread-safe.

The numbered requirements:

  • R1. A vehicle enters and gets a ticket naming its spot and entry time.
  • R2. A vehicle exits with its ticket, the spot is freed and the fee is returned.
  • R3. A vehicle only parks in a spot that fits it.
  • R4. The smallest fitting spot type is used.
  • R5. A full lot refuses a vehicle with a clear reason.
  • R6. The same plate cannot be parked twice at once.
  • R7. A ticket works once.

Out of scope for this round: payment, reservations, electric vehicle charging and display boards. Saying "out of scope" aloud is part of the answer.

Out of scope

Out of scope means a feature that was named and deliberately left out of this design, so time goes to the core.

Example: payment and reservations in this parking lot.

Check yourself: 1. Which spot types fit a car? 2. Why is the smallest fitting spot chosen? 3. Name two things left out of scope.