general hierarchy Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > pattern > design pattern > general hierarchy

Next design pattern: immutable Up: design pattern Previous design pattern: facade

general hierarchy comparison table

Subject have solution have related patterns have context have forces have problem has definition have antipatterns is a subtopic of is a kind of is an instance of

design pattern zero or more related design patterns a context one or more forces a sentence or two explaining the main difficulty being tackled A pattern useful for the design of software zero or more antipatterns - solutions that are inferior or do not work in this context with the reason for their rejection 6.1 - Introduction to Patterns pattern

general hierarchy
Create an abstract ŤNodeť class to represent the features possessed by each object in the hierarchy.
Then create at least two subclasses of the ŤNodeť class.
One of the subclasses, ŤSuperiorNodeť, must be linked by a Ťsubordinatesť association to the superclass; whereas at least one subclass, ŤNonSuperiorNodeť, must not be.
The subordinates of a ŤSuperiorNodeť can thus be instances of either ŤSuperiorNodeť or ŤNonSuperiorNodeť.
the Reflexive Association pattern, the Composite pattern (a specialization of the General Hierarchy pattern) many class diagrams where you often find a set of objects that have a naturally hierarchical relationship.
You want a flexible way of representing the hierarchy that naturally prevents certain objects from having subordinates
You also have to account for the fact that all the objects share common properties and operations
How do you draw a class diagram to represent a hierarchy of objects, in which some objects cannot have subordinates? 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 modelling a hierarchy of categories using a hierarchy of classes 6.3 - The General Hierarchy Pattern design pattern

Subject	have solution	have related patterns	have context	have forces	have problem	has definition	have antipatterns	is a subtopic of	is a kind of	is an instance of
design pattern		zero or more related design patterns	a context	one or more forces	a sentence or two explaining the main difficulty being tackled	A pattern useful for the design of software	zero or more antipatterns - solutions that are inferior or do not work in this context with the reason for their rejection	6.1 - Introduction to Patterns	pattern
general hierarchy	Create an abstract ŤNodeť class to represent the features possessed by each object in the hierarchy. Then create at least two subclasses of the ŤNodeť class. One of the subclasses, ŤSuperiorNodeť, must be linked by a Ťsubordinatesť association to the superclass; whereas at least one subclass, ŤNonSuperiorNodeť, must not be. The subordinates of a ŤSuperiorNodeť can thus be instances of either ŤSuperiorNodeť or ŤNonSuperiorNodeť.	the Reflexive Association pattern, the Composite pattern (a specialization of the General Hierarchy pattern)	many class diagrams where you often find a set of objects that have a naturally hierarchical relationship.	You want a flexible way of representing the hierarchy that naturally prevents certain objects from having subordinates You also have to account for the fact that all the objects share common properties and operations	How do you draw a class diagram to represent a hierarchy of objects, in which some objects cannot have subordinates?	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	modelling a hierarchy of categories using a hierarchy of classes	6.3 - The General Hierarchy Pattern		design pattern

Next design pattern: immutable Up: design pattern Previous design pattern: facade