Course contentsShow
← Software Engineering
Lesson 196 of 1,9336. SOLID PrinciplesFree lesson

The Axis of Change Concept

Understand how different stakeholders create different axes of change that should be separated into distinct modules.

The Axis of Change Concept

What you'll learn: How different stakeholders create different reasons for code to change, and why those reasons should live in separate modules.


When we talk about the "axis of change," we're identifying who or what might cause a particular piece of code to change. Different stakeholders have different concerns, and each concern represents a different axis.

Understanding the Axis Metaphor

Think of your codebase as having multiple dimensions. One dimension might be "business logic changes requested by product managers." Another might be "database schema changes requested by DBAs." Yet another could be "UI layout changes requested by designers." Each of these is an axis of change—a direction along which your code might need to evolve.

When code mixes responsibilities from multiple axes, changes become dangerous. If your single class handles both business calculations and formats reports, then the finance team and the marketing team both have reasons to modify it. Their changes might conflict or accidentally break each other's functionality.

Separating the Axes

The Single Responsibility Principle asks you to identify these axes and keep them separate. If the finance team needs business rule changes, they should touch only the calculation module. If marketing needs different report layouts, they should touch only the formatting module.

The goal: When a stakeholder requests a change, you should be able to point to exactly one module that needs modification. No ripple effects, no tangled dependencies.

Key Takeaway: Each stakeholder represents a potential axis of change—group code so that each axis affects only one module, minimizing cross-stakeholder conflicts and change propagation.