CSE Roadmap

Core tier · about 2 hours · 7 parts

Part 6 of 7 · 1 min read

Leaving things out

A small correct design beats a large half-finished one.

Leaving things out

Scope is a choice. Interviewers reward candidates who say, "Repeating bookings are out of scope for now, but here is where they would plug in." That sentence shows the design has a place for growth without paying for it today.

Habits that help: - State out-of-scope items at the start, and have the interviewer agree. - Name one extension point for the likeliest change. For the room system, TimeSlot could grow into a repeat rule. - Do not leave a promise unmet. If the list says "search", the class list must have a place for it.

Interview angle

Answer in your head first, then open it.

How do you find the classes?

Read the requirements for nouns, keep the ones with identity or rules, and turn the rest into attributes, values or enums.

How do you decide scope?

Ask, write it down, name what is out, and say where the extension would go.

Where does a rule like no overlap belong?

With the class that can see all the data it needs, here the booking service.

Check yourself: 1. Why name an extension point for something out of scope? 2. What goes wrong if a listed requirement has no class? 3. Who must agree on the scope?

Words you will meet

Word Meaning
Functional requirement Something the system must do
Non-functional requirement A quality the system must have, such as speed or safety
Entity A tracked thing told apart by an id
Value object A thing defined only by its data
Attribute A fact about an entity, such as capacity
Enum A small fixed set of named values
Scope What the design covers, and what it does not