Explore Topics
📋
UML Class Diagram Overview
The static blueprint of your object-oriented system
🏗️ Class Box Builder — Explore UML Notation
+ public- private# protected~ packageunderline = staticitalic = abstract
📋
UML Class Diagram Overview
The static blueprint of your object-oriented system
A UML class diagram is a structural diagram that shows the static view of an application. It describes the types of objects in a system and the structure of each class — its name, attributes, and operations. Class diagrams do not show runtime behavior; they capture the design-time structure. Every class is represented as a rectangular box divided into three horizontal compartments: the top for the class name, the middle for attributes (data), and the bottom for operations (behavior). Class diagrams are the most commonly used UML diagram and serve as the foundation for code generation, design reviews, and team communication.
Key Ideas
- A class diagram shows the static structure — classes, attributes, and operations
- It does NOT show runtime behavior (use Sequence or Activity diagrams for that)
- Most commonly used UML diagram — the foundation for many other diagrams
- Every class is a rectangular box with three compartments
- Top compartment: class name — Middle: attributes — Bottom: operations
- Used for analysis (understanding the domain) and design (planning the code)
- Supports forward engineering (diagram → code) and reverse engineering (code → diagram)
Strengths
- ✦Provides a bird's-eye view of system structure at a glance
- ✦Language-agnostic — same notation works for Java, C#, Python, etc.
- ✦Serves as a communication tool between developers, architects, and stakeholders
- ✦Foundation for code generation tools and IDE integrations
Weaknesses
- △Cannot express runtime behavior or execution order
- △Can become cluttered for very large systems — need to scope diagrams
- △Requires discipline to keep diagrams in sync with evolving code
- △Students often confuse class diagrams with ER diagrams (database-focused)
Used in:Most Java IDEs (IntelliJ IDEA, Eclipse) can generate class diagrams from source code automatically — this is reverse engineering. Conversely, tools like Visual Paradigm and Enterprise Architect can generate Java class skeletons from class diagrams — forward engineering.
Code Snippets
Quiz
UML Class Diagram Overview Quiz
QUIZ 1/6What does the middle compartment of a UML class box contain?
Diagrams
Practice
Place each element into the correct compartment of a UML class box:
EXERCISE 1/4Student (bold, centered)
- name : String
- gpa : double = 0.0
+ <<create>> Student(name: String)
+ getName() : String
+ setGpa(g: double) : void
# id : int {readOnly}
Top Compartment (Name)
Middle Compartment (Attributes)
Bottom Compartment (Operations)
Complete the UML Class Box Notation
EXERCISE 2/4Visibility Markers:
= public
= private
= protected
~ = package
Attribute format:
visibility : Type
Abstract class name is shown in
Static members are shown with
UML Class Box Myths
EXERCISE 3/4Constructors go in the middle compartment (attributes section) of a class box.
A forward slash (/) before an attribute name means it is derived (computed from other values).
Static members in UML are shown in bold text.
In UML, omitting the visibility marker means the member is public by default.
The <<interface>> stereotype is used to mark a class that contains only operation signatures.
Abstract methods are shown in italic to indicate they have no implementation.
Match each visibility marker to its access level:
EXERCISE 4/4+ (plus)
- (minus)
# (hash)
~ (tilde)
Public — visible to all
Private — visible only within class
Protected — class + subclasses
Package — same package only