![]() |
subject > pattern > design pattern > abstraction-occurrence |
![]() ![]() | ||||
abstraction-occurrence | ||||
subject | fact |
abstraction-occurrence | has definition A pattern in which two classes are related by an association, and one of the classes represents an abstraction of the other | ![]() |
has antipatterns
| ![]() | |
has context class diagrams that form part of a system domain model | ![]() | |
has forces
| ![]() | |
has problem What is the best way to represent sets of occurrences in a class diagram? | ![]() | |
has references a generalization of the Title-Item pattern of Eriksson and Penker | ![]() | |
has related patterns Abstraction-Occurrence Square pattern if the abstraction is an aggregate (and the occurrences are also aggregates) | ![]() | |
has solution
| ![]() | |
is a subtopic of 6.2 - The Abstraction-Occurrence Pattern | ![]() | |
is an instance of design pattern | ![]() | |
design pattern | has name | ![]() |
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: adapter Up: design pattern Previous design pattern: singleton