Why this matters
- Lifelines — detailed pointwise breakdown in the section below.
- Messages — detailed pointwise breakdown in the section below.
- Return values — detailed pointwise breakdown in the section below.
- CampusOS book ticket flow — detailed pointwise breakdown in the section below.
- Whiteboard clarity often decides pass/fail before code depth.
1. ClarifyRequirements + scope
2. EntitiesNouns, verbs, ownership
3. APIsPublic operations
4. Class diagramRelationships
5. PatternsWhere they earn their keep
6. CodeCore paths + edge cases
Overview
Show how objects collaborate over time for one use case. Study each section below in order — every list is interview-ready reference material.
Lifelines
Points to cover
- Definition — what Lifelines 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
- Messages
- Return values
- CampusOS book ticket flow
Test yourself
Answer these before moving on — recall is what makes it stick.