UML & Class Diagrams
The problem
Discussing a class design in prose or code alone makes it hard to see the overall shape of a system at a glance — relationships, multiplicities, and inheritance hierarchies are exactly the kind of structure a diagram communicates faster and less ambiguously than a paragraph or a wall of code.
Why now
Object-oriented programming basics and inheritance already established the concepts (classes, fields, methods, is-a, has-a relationships) that need a shared visual vocabulary; UML class diagrams are that vocabulary, letting a design be communicated and reviewed before a single line of code is written.
Mental model
A UML class diagram is a picture of exactly what a class declaration already says — its name, fields, and methods — plus arrows for the relationships between classes (inheritance, composition, association) that would otherwise require reading multiple files to piece together. It's a communication tool, not a formalism to memorize for its own sake: the goal is a shared, quick-to-scan picture of a design's shape.
Requires
- Object-Oriented Programming BasicsLow-Level Design
A class diagram visualizes exactly the class structure (fields, methods) object-oriented-programming-basics defines; you need the underlying concept before a notation for drawing it is meaningful.
Unlocks
Used in
- System design and LLD interviews, where sketching a class diagram is often the expected first step
- Design documents and architecture reviews communicating a class structure before implementation
- Reverse-engineering an unfamiliar codebase's structure by sketching its classes and relationships
- Onboarding new engineers to a system's object model quickly
Projects
- Draw a UML class diagram for a small system (e.g. a library management system) showing classes, key fields/methods, and inheritance/composition relationships
- Given an existing small codebase, reverse-engineer and draw its class diagram from the code alone
Examples
- An open arrowhead from Circle to Shape denotes inheritance ('is-a'); a filled diamond from Car to Engine denotes composition ('has-a')
- A quick whiteboard class diagram in an interview communicates a design's shape in 30 seconds that would take several minutes to explain in prose
Resources
- UML Class Diagrams — a guidearticle
Mastery checklist
- I can draw a class diagram showing fields, methods, and relationships for a small system
- I can distinguish inheritance, composition, and association arrows in a diagram
- I can reverse-engineer a class diagram from existing code
- I can use a class diagram to communicate a design before writing implementation code