
doi: 10.1109/ecbs.2006.31
Patterns help transporting knowledge and provide common names for solutions. Architects need a lot of experience to create long-lasting system architectures and should benefit from experiences written down in patterns. The description of architecture patterns and design patterns usually focuses on structures in software. This renders the patterns of limited use for architects who need to structure a system before they choose a structure for the implementing software. Therefore, architects need an additional kind of patterns with an adequate notation. This paper introduces the category of conceptual patterns which focus on system structure in the description of problem and solution. Architects can benefit from the solutions described by conceptual patterns when analyzing systems and in early phases of system design. Extracting the conceptual part of existing patterns is a first step to find conceptual patterns. Usually, a set of patterns is arranged in a pattern language for a problem domain. This paper shows some examples of conceptual patterns extracted from existing architecture and design patterns.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 9 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
