Why this matters
- Customer inserts card and enters PIN to start authenticated session
- Scope — what "Session lifecycle" covers inside ATM System and what it does not
- Scope — what "Dispenser chain" covers inside ATM System and what it does not
- Scope — what "Concurrency" covers inside ATM System and what it does not
- Machine problems test State, Strategy, and facade coordination.
Client / API
FacadeSingle entry point
EntitiesDomain objects
State / Strategy
CampusOS context
CampusOS is the fictional smart-campus platform used across this track. Treat this module as a real product slice:
Context
- Belongs to CampusOS — same naming and design vocabulary as parking, library, and booking modules
- Scope is one JVM — persistence is in-memory or behind a repository interface
- Goal is a class diagram + core Java that an interviewer can follow in 35–45 minutes
- Extension paragraph at the end links to System Design when scale exceeds one process
Requirements snapshot
Functional requirements
- Customer inserts card and enters PIN to start authenticated session
- Check balance, withdraw cash, deposit (optional), transfer between accounts
- Cash dispenser tracks note counts per denomination
- Session timeout ends authenticated context
- Failed PIN attempts lock card after threshold
- Print receipt for each successful transaction
Non-functional requirements
- Single JVM, in-process design for this LLD article
- Core flows testable with in-memory repositories
- Extension points for new rules without editing central god classes
- Clear public API on facade/service layer
- CampusOS extension links to System Design when scale demands distribution
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 · 6 sections
- Overview
- Requirements
- Session lifecycle
- Dispenser chain
- Concurrency
- CampusOS extension
Test yourself
Answer these before moving on — recall is what makes it stick.