CSE Roadmap

Core tier · about 2 hours · 9 parts

Part 7 of 9 · 1 min read

A full requirements round

One complete requirements round for a small system, from the vague request to the written list.

The request: "Design a way for students to share notes."

Questions and answers. (The answers are made up for this example.)

  • What can a student do? Upload a note, search for notes by subject, download a note.
  • Who uses it? Students of one university, on phones and laptops.
  • How many? 20,000 students, about 15 percent active each day.
  • How big is a note? About 2 megabytes, mostly PDF.
  • How fast? Search results in under one second.
  • What must never be lost? Uploaded notes.
  • Can a note be edited by others? No, in version one.

The written result.

Item Decision
Core features Upload, search by subject, download
Later features Comments, ratings, sharing groups
Out of scope Real-time editing, payments
Users 20,000 students, so 20,000 × 0.15 = 3,000 daily active users
Speed 99 out of 100 searches finish in under 1 second
Must not lose Uploaded notes
Assumption 3 uploads per active student per month

A short check. How many uploads per month? 3,000 active students × 3 = 9,000 uploads. At 2 megabytes each, that is 18,000 megabytes, about 18 gigabytes a month. Over a year, about 216 gigabytes. That is small. It fits comfortably on one storage service, and the requirement "must not lose notes" is the one that most needs a good answer, through backups and copies.

The requirements round took ten minutes and produced the three things the design will rely on: a scope, a set of numbers and a list of what must never fail.

Check yourself:

  • What would change in the design if the university had 2,000,000 students and not 20,000?
  • Which requirement in the table most needs backups?