Content deleted Content added
No edit summary |
No edit summary |
||
Line 12:
| isbn = 9780201750447
| accessdate = 2012-05-29
}}</ref> This is an often-stated{{weasel word}} principle of OOP, such as in the influential book ''[[Design Patterns]]'' (1994).<ref>{{Cite book | isbn = 0-201-63361-2 | title = [[Design Patterns|Design Patterns: Elements of Reusable Object-Oriented Software]] | last1 = Gamma | first1 = Erich | authorlink1 = Erich Gamma | last2 = Helm | first2 = Richard | last3 = Johnson | first3 = Ralph | authorlink3 = Ralph Johnson (computer scientist) | last4 = Vlissides | first4 = John | authorlink4 = John Vlissides | year = 1994 | publisher = [[Addison-Wesley]] | page = [https://archive.org/details/designpatternsel00gamm/page/20 20] | oclc = 31171684 }}
</ref>
Line 231:
}}</ref>
Initial design is simplified by identifying system object behaviors in separate interfaces instead of creating a hierarchical relationship to distribute behaviors among business-___domain classes via inheritance. This approach more easily accommodates future requirements changes that would otherwise require a complete restructuring of business-___domain classes in the inheritance model. Additionally, it avoids problems often
Composition relation is more flexible as it may be changed on runtime, while sub-typing relations are static and need recompilation in many languages.
| |||