Pattern representation by example can be extremely useful. Sometimes, example can be used as a description of the pattern. Most of the time people will be able to abstract away from an example to a pattern with relative ease. This presentation will concentrate on representing patterns by example using a tool developed by Delta Software Technology called Pattern By Example.
The product name PBE is derived from the term "Pattern By Example", which characterizes the central product idea: the development technique based on examples, known in a similar form as "Query By Example". In concrete terms, this means the following: a developer would like to reuse the structures of an existing source at another place. Normally, the entire source would then be copied and manually modified until the original structures are adjusted to a new context. If a further situation arises to which the existing source is structurally suited, this process is repeated. This intuitive procedure is automated and improved while using PBE. [4]
PBE enables you to define so-called "Code Patterns", store the respective definition, and re-use it. The terms "Code Pattern", "Pattern", "Code Template", and "Template" are used as synonyms here. A "Code Pattern" is a re-usable, specified code fragment that can be parameterized and configured; a further characteristic is its linkage to one or more programming languages. In contrast, the "Design Patterns" known from literature have a universal character with respect to their usability, i.e. they are language-independent and are only linked to particular concepts and paradigms. Furthermore, these Design Patterns normally relate to several source modules and code sections at any one time. In an individual case, a Code Pattern can be the language-specific realization of a Design Pattern.[4]