UML and Object-Oriented Design

5.

Object-Oriented Design Principles

5.1.

SOLID Principles

5.1.1.

Single Responsibility Principle

5.1.1.1.

Definition and Rationale

5.1.1.2.

Identifying Responsibilities

5.1.1.3.

Cohesion and Coupling

5.1.1.4.

Refactoring for SRP

5.1.1.5.

Benefits and Trade-offs

5.1.2.

Open/Closed Principle

5.1.2.1.

Definition and Rationale

5.1.2.2.

Extension vs. Modification

5.1.2.3.

Use of Abstraction

5.1.2.4.

Strategy Pattern Application

5.1.2.5.

Benefits and Trade-offs

5.1.3.

Liskov Substitution Principle

5.1.3.1.

Definition and Rationale

5.1.3.2.

Behavioral Subtyping

5.1.3.3.

Contract Compliance

5.1.3.4.

Common Violations

5.1.3.5.

Design by Contract

5.1.4.

Interface Segregation Principle

5.1.4.1.

Definition and Rationale

5.1.4.2.

Client-Specific Interfaces

5.1.4.3.

Avoiding Fat Interfaces

5.1.4.4.

Interface Decomposition

5.1.4.5.

Benefits and Trade-offs

5.1.5.

Dependency Inversion Principle

5.1.5.1.

Definition and Rationale

5.1.5.2.

High-Level vs. Low-Level Modules

5.1.5.3.

Dependency Injection

5.1.5.4.

Inversion of Control

5.1.5.5.

Benefits and Trade-offs

5.2.

Additional Design Principles

5.2.1.

Don't Repeat Yourself

5.2.2.

5.2.3.

Composition over Inheritance

5.2.4.

Program to Interfaces

5.2.5.

Favor Object Composition

Previous

4. Behavioral UML Diagrams

Go to top

Next

6. Design Patterns in UML