CSE Roadmap

Core tier · about 2 hours · 9 parts

Part 6 of 9 · 1 min read

Hidden requirements

The needs nobody mentions, and how to find them by asking about failure and growth.

Think of buying a house. The seller talks about the garden and the kitchen. Nobody mentions the old pipes, until the first cold winter.

Systems have hidden requirements too. Nobody mentions them, because nobody thinks about them until something breaks. Four questions bring them out.

  1. What must never be lost? Orders, payments and messages are usually in this group. A lost photo comment is not.
  2. What happens when a part fails? Should the service keep running with fewer features, or stop completely?
  3. How does the load change? Is traffic steady, or does it spike during a sale, a match or a deadline?
  4. Who must not see this data? Private messages, health records and payment details need strong protection.

The answers change the design. If a lost message is unacceptable, the design needs copies of the data. If traffic spikes ten times for one hour, the design needs a plan for that hour.

Failure

A failure is a moment when the system stops doing what it promised. A fault is one part going wrong. A good design keeps a fault from becoming a failure.

Example: one server crashing is a fault. If a second server takes over and users notice nothing, the system had a fault but no failure.

Interview angle

Answer in your head first, then open it.

How do you find the requirements that nobody mentions?

Interviewers often watch for the candidate who asks "what happens when this fails?" without being prompted. It shows experience, because people who have run real systems know that parts fail every day.

Check yourself:

  • Which of the four questions would you ask for a bank transfer system? Why?
  • What is the difference between a fault and a failure?