abstraction-occurrence Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

subject > pattern > design pattern > abstraction-occurrence

Next design pattern: adapter Up: design pattern Previous design pattern: singleton

abstraction-occurrence comparison table

Subject have solution have related patterns have references 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 one or more references which indicate who developed or inspired a pattern 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

abstraction-occurrence
Create an ŤAbstractionť class that contains the data that is common to all the members of a set of occurrences.
Then create an ŤOccurrenceť class representing the occurrences of this abstraction.
Connect these classes with a one-to-many association
Abstraction-Occurrence Square pattern if the abstraction is an aggregate (and the occurrences are also aggregates) a generalization of the Title-Item pattern of Eriksson and Penker class diagrams that form part of a system domain model
You want to represent the members of each set of occurrences without duplicating the common information
You want a solution that maximizes the flexibility of the system
What is the best way to represent sets of occurrences in a class diagram? A pattern in which two classes are related by an association, and one of the classes represents an abstraction of the other
using a single class
creating a separate abstraction subclass for each occurrence
making the abstraction class a superclass of the occurrence class
6.2 - The Abstraction-Occurrence Pattern design pattern

Subject	have solution	have related patterns	have references	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	one or more references which indicate who developed or inspired a pattern	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
abstraction-occurrence	Create an ŤAbstractionť class that contains the data that is common to all the members of a set of occurrences. Then create an ŤOccurrenceť class representing the occurrences of this abstraction. Connect these classes with a one-to-many association	Abstraction-Occurrence Square pattern if the abstraction is an aggregate (and the occurrences are also aggregates)	a generalization of the Title-Item pattern of Eriksson and Penker	class diagrams that form part of a system domain model	You want to represent the members of each set of occurrences without duplicating the common information You want a solution that maximizes the flexibility of the system	What is the best way to represent sets of occurrences in a class diagram?	A pattern in which two classes are related by an association, and one of the classes represents an abstraction of the other	using a single class creating a separate abstraction subclass for each occurrence making the abstraction class a superclass of the occurrence class	6.2 - The Abstraction-Occurrence Pattern		design pattern

Next design pattern: adapter Up: design pattern Previous design pattern: singleton