Pattern Oriented Software Architecture Volume 5: On Patterns and Pattern Languages

Pattern Concept Summary

This appendix summarizes key pattern terms that we use and define in greater detail within the book. When a definition consists of other terms also defined here, we italicize these terms. The focus here is explicitly on software and its development, otherwise terms such as ‘architecture’ and ‘design’ would obviously have far broader scope.
Analysis Pattern	A pattern that describes how to model a particular kind of problem in a business domain.
Anti-Pattern	See Dysfunctional Pattern.
Architectural Style	The key software architecture decisions common across a number of different architectures that are considered at one level equivalent. Architectural style allows the characterization and comparison of similar and dissimilar architectures.
Architecture	See Software Architecture.
Benefits	The consequences of a pattern that are considered beneficial.
Code Smell	A code-level problem that creates the motivation and context for refactoring. A code smell may have arisen from or be equivalent to a dysfunctional pattern.
Composite Pattern	See Pattern Compound.
Compound Pattern	See Pattern Compound.
Consequences	The results of applying a pattern. Consequences may be characterized in terms of benefits and liabilities.
Context	The situation in which a pattern is applied. The context can be characterized in general terms, describing general properties of an environment or, in specific terms, describing the preceding patterns that might have been ...