Object Oriented Software Engineering   View all facts   Glossary   Help | 
| subject > pattern > design pattern > general hierarchy | 
| general hierarchy | ||||
| subject | fact | |||
| general hierarchy | has definition A pattern in which two classes are related both by a generalization and by a one to many association, such that the generated graph of instances forms a hierarchy | ![]()  | 
| has antipatterns modelling a hierarchy of categories using a hierarchy of classes | ![]()  | |
| has context many class diagrams where you often find a set of objects that have a naturally hierarchical relationship. | ![]()  | |
| has forces | ![]()  | |
| has problem How do you draw a class diagram to represent a hierarchy of objects, in which some objects cannot have subordinates? | ![]()  | |
| has related patterns the Reflexive Association pattern, the Composite pattern (a specialization of the General Hierarchy pattern) | ![]()  | |
has solution 
  | ![]()  | |
| is a subtopic of 6.3 - The General Hierarchy Pattern | ![]()  | |
| is an instance of design pattern | ![]()  | |
| design pattern | has name | ![]()  | 
| has references one or more references which indicate who developed or inspired a pattern | ![]()  | |
| should be illustrated using a simple diagram | ![]()  | |
| should be written using a narrative writing style | ![]()  | |
| pattern | should be as general as possible | ![]()  | 
| should be described in an easy-to-understand form so that people can determine when and how to use it | ![]()  | |
| should contain a solution that has been proven to effectively solve the problem in the indicated context | ![]()  | 
Next design pattern: immutable     Up: design pattern    Previous design pattern: facade