Why this matters
- Classes and interfaces — detailed pointwise breakdown in the section below.
- Relationships — detailed pointwise breakdown in the section below.
- Multiplicity — detailed pointwise breakdown in the section below.
- What to skip — detailed pointwise breakdown in the section below.
- Whiteboard clarity often decides pass/fail before code depth.
ParkingLotentry facade
ParkingFloorcollection of spots
Ticketissued on entry
Vehiclecar, bike, truck
ParkingSpot links Vehicle when occupied; Strategy picks spot by vehicle type.
Overview
The notation you actually need on a whiteboard — nothing more. Study each section below in order — every list is interview-ready reference material.
Classes and interfaces
Points to cover
- Definition — what Classes and interfaces means in one clear sentence
- When to use — the force or smell that triggers this concept
- CampusOS example — where this appears in parking, booking, or library modules
- How to explain — pointwise bullets you can say aloud in an interview
- Common mistake — what weak candidates do instead
- Refactor move — one concrete change that improves the design
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Relationships
- Multiplicity
- What to skip
Test yourself
Answer these before moving on — recall is what makes it stick.