SOLID Principles

Single-Responsibility Principle (SCP)

A class should have one, and only one, reason to change. An object should have only one responsibility (a reason to change). It is supposed to simplify modifications. The cohesion is stronger, dependency coupling is looser and the code is less complex.

Open-Closed Principle (OCP)

Entities should be open for extension, but closed for modification. Entity can be extended by adding what is needed, but it can never be modified. This significantly reduces the risk of breaking existing functionality and provides a looser coupling.

Liskov Substitution Principle (LSP)

Subtypes must be substitutable for their base types. The principle says that it is possible to use base type and get a correct result as the outcome. It can be said that the LSP confirmes abstractions are correct.

Interface Segregation Principle (ISP)

Classes that implement interfaces, should not be forced to implement methods they do not use. Big interfaces should be splitted into smaller ones so there are no methods that are not used implemented. Classes know only about methods related to them providing decoupling and easier modifications.

Dependency Inversion Principle (DIP)

High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions. This reduces dependencies in the code modules. Code is much more easier to maintain if abstractions and details are isolated from each other.

Similar posters

The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...
STEEPLED STEEPLED - Social, Technological, Economical, Environmental, Political, Legal, Ethical and additional compared to STEEPLE is Demographic.
BLUF - Bottom Line Up Front
BLUF - Bottom Line Up Front BLUF is a framework for declaring the purpose of the message and the action required. It should provide the most important information.
Transactional Analysis
Transactional Analysis Transactional Analysis is a psychoanalytic theory and method of therapy. A personality is made up of three ego states: Parent, Adult, Child.