Principles Wiki

User Tools

Site Tools

You are here: Principles Wiki » Principles » Open-Closed Principle (OCP)
principles:open-closed_principle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
principles:open-closed_principle [2020-10-12 12:37] – old revision restored (2013-01-30 15:04) 159.69.186.191principles:open-closed_principle [2020-10-12 12:37] – old revision restored (2013-01-30 14:49) 159.69.186.191
Line 1: Line 1:
-====== Open-Closed Principle ======+====== Open-closed Principle [see ECV] ======
  
-===== Variants and Alternative Names ===== +~~REDIRECT>principles:Encapsulate the Concept that Varies~~
- +
- +
-===== Context ===== +
-/* fill in contexts here: */ +
-  * [[contexts:Object-Oriented Design]]  +
- +
- +
-===== Principle Statement ===== +
- +
-Modules should be open for enhancement but closed for modification. +
- +
- +
-===== Description ===== +
- +
- +
-===== Rationale ===== +
- +
- +
-===== Strategies ===== +
- +
- +
-===== Origin ===== +
- +
-Bertrand Meyer: //[[http://en.wikipedia.org/wiki/Object-Oriented%20Software%20Construction|Object-Oriented Software Construction]]//, p. 57pp. +
- +
-===== Evidence ===== +
-/* Comment out what is not applicable and explain the rest: */ +
-/* +
-  * [[wiki:Proposed]] +
-  * [[wiki:Examined]] +
-  * [[wiki:Accepted]] +
-  * [[wiki:Questioned]] +
-*/ +
- +
-===== Relations to Other Principles ===== +
- +
-==== Generalizations ==== +
- +
-  * [[Encapsulate the Concept that Varies]] (ECV): The OCP demands encapsulating abstract concepts in base classes (or interfaces) in order to be able to enhance the module by subclassing which is possible without changing the previously written code. In this case several variations of a concept may exist in the code at the same time. There is always the abstract base class plus one or usually more concrete subclasses. So the OCP is about encapsulating abstract concepts that vary "in space". +
- +
-==== Specializations ==== +
- +
-==== Contrary Principles ==== +
- +
-  * [[more Is More Complex]] (MIMC): The OCP demands introducing abstract base classes or interfaces. +
-  * [[Keep It Simple Stupid]] (KISS): The OCP demands introducing abstract base classes or interfaces. This increases complexity. +
-  * [[Model Principle]] (MP): OCP sometimes results in the introduction of artificial classes that do not correspond to a real-world concept. +
- +
-==== Complementary Principles ==== +
- +
-  * [[Dependency Inversion Principle]] (DIP): OCP results in the introduction of abstract classes or interfaces and descendant concrete classes. DIP now tells that other classes should only depend on the abstractions. +
-  * [[Liskov Substitution Principle]] (LSP): OCP may results in the introduction of abstract classes or interfaces. Here it is important to get the abstraction right. Otherwise LSP may be violated. +
- +
-==== Principle Collections ==== +
- +
-{{page>collections:SOLID#Box}} +
-{{page>collections:Principles in "Object-Oriented Software Construction"#Box}} +
- +
-===== Example ===== +
- +
- +
-===== Description Status ===== +
-/* Choose one of the following and comment out the rest: */ +
-[[wiki:Stub]] +
-/*[[wiki:Incomplete]]*/ +
-/*[[wiki:Complete]]*/ +
- +
-===== Further Reading ===== +
- +
-  * Robert C. Martin: //Agile Software Development, Principles, Patterns, and Practices//, p. 99pp. +
-  * [[http://www.butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod|ButUncleBob: Principles of OOD]]+
principles/open-closed_principle.txt · Last modified: 2022-03-02 23:55 by tory