Loading content
The SOLID principles are a set of five design principles formulated by Robert C. Martin. They aim to increase the maintainability and flexibility of software by providing clear guidelines for structuring classes and their interactions. These principles are: Single Responsibility Principle (SRP), Open/Closed Principle (OCP), Liskov Substitution Principle (LSP…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
The SOLID principles are five guidelines for object-oriented design that structure responsibilities, dependencies, and extensibility.
The five letters bundle design principles that Robert C. Martin popularized in object-oriented software development from the 1990s onward. They build on older ideas about coupling, cohesion, abstraction, and substitution.
SOLID is a lens for change boundaries: one responsibility should have a focused reason to change, dependencies should point to abstractions, and subtypes must honor their contracts. The principles are guidance, not templates.
Eine Einheit bündelt eine zusammengehörige Änderungsursache.
Ein Entwurf lässt Erweiterung zu, ohne bewährten Code unnötig zu verändern.
Höhere und niedrigere Komponenten hängen von stabilen Abstraktionen ab.
SOLID provides shared language for code reviews and refactoring and can limit change propagation. Overuse creates needless abstractions and complicates simple code; actual change patterns should decide.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.