principles:encapsulate_the_concept_that_varies
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
principles:encapsulate_the_concept_that_varies [2013-01-30 16:10] – improved Further Reading christian | principles:encapsulate_the_concept_that_varies [2020-10-12 16:09] – old revision restored (2013-04-05 12:28) 159.69.186.191 | ||
---|---|---|---|
Line 47: | Line 47: | ||
* Visitor: New operations have to be added to a given more or less static inheritance structure of classes. | * Visitor: New operations have to be added to a given more or less static inheritance structure of classes. | ||
* ... | * ... | ||
+ | |||
+ | ===== Caveats ===== | ||
+ | |||
+ | See section [[#contrary principles]]. | ||
+ | |||
===== Origin ===== | ===== Origin ===== | ||
+ | |||
+ | The principle is stated, explained and used in the GoF book: | ||
Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: // | Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides: // | ||
+ | But the idea if ECV is actually much older. It was first presented in | ||
+ | |||
+ | David Parnas: // | ||
===== Evidence ===== | ===== Evidence ===== | ||
/* Comment out what is not applicable and explain the rest: */ | /* Comment out what is not applicable and explain the rest: */ | ||
Line 64: | Line 74: | ||
==== Generalizations ==== | ==== Generalizations ==== | ||
- | |||
- | * [[Generalization Principle]] (GP): Encapsulating a varying concept typically results in a more generally applicable solution. This is especially true when an abstract concept is encapsulated by introducing an interface or an abstract class. | ||
==== Specializations ==== | ==== Specializations ==== | ||
Line 75: | Line 83: | ||
* **[[More Is More Complex]] (MIMC)**: ECV demands adding a new class for a new varying concept. | * **[[More Is More Complex]] (MIMC)**: ECV demands adding a new class for a new varying concept. | ||
- | * [[Keep It Simple Stupid]] (KISS): ECV demands adding a new class for a new varying concept. This adds complexity. | ||
* [[Model Principle]] (MP): ECV sometimes results in classes which do not correspond top a real-world concept in the sense of MP. A " | * [[Model Principle]] (MP): ECV sometimes results in classes which do not correspond top a real-world concept in the sense of MP. A " | ||
==== Complementary Principles ==== | ==== Complementary Principles ==== | ||
- | * [[Dependency Inversion Principle]] (DIP): ECV may result | + | * [[Low Coupling]] (LC): ECV results |
* [[Liskov Substitution Principle]] (LSP): ECV may result in the introduction of an abstract base class. Here it is important to get the abstraction right. Otherwise LSP may be violated. | * [[Liskov Substitution Principle]] (LSP): ECV may result in the introduction of an abstract base class. Here it is important to get the abstraction right. Otherwise LSP may be violated. | ||
- | + | * [[Generalization Principle]] (GP): Encapsulating a varying concept typically results in a more generally applicable solution. This is especially true when an abstract concept is encapsulated by introducing an interface or an abstract class. | |
+ | * [[Dependency Inversion Principle]] (DIP): ECV may result in the introduction of an abstract base class. Here DIP demands that other classes should only depend on this new abstract base class and not on the concrete subclasses. | ||
+ | * [[Information Hiding/ | ||
==== Principle Collections ==== | ==== Principle Collections ==== | ||
Line 89: | Line 97: | ||
- | ===== Example | + | ===== Examples |
Line 104: | Line 112: | ||
* [[Single Responsibility Principle]] | * [[Single Responsibility Principle]] | ||
* [[Open-Closed Principle]] | * [[Open-Closed Principle]] | ||
+ |
principles/encapsulate_the_concept_that_varies.txt · Last modified: 2021-10-18 21:31 by christian