A EuroPLoP 2001 Design Fest
Klaus Marquardt <pattern@kmarquardt.de>
Motivation
Every software engineer has used techniques to increase the execution speed of the system under development. Some of these techniques are purely technical, i.e. using a more efficient algorithm, others focus on correct distribution of tasks among different system parts, or on feature avoidance. Engineers working in different areas such as databases, embedded systems, or distributed systems, are used to apply specific techniques that are apparently different to techniques used in other domains. Nevertheless, I have found that these techniques parallel each other to a surprisingly high degree. There seem to be a number of Performance Patterns yet undiscovered.
Purpose
The purpose of this Design Fest or Focus Group is to substantiate my claim by actually starting a Performance Pattern Language. We will explore what kind of patterns are known to us, how they relate each other, and what more patterns may be around. We will start a classification or taxonomy, sort the available patterns, and identify missing patterns by analogy. Finally we will start to write the actual patterns.
We need some prepared material as a starting point, so all attendees have to submit a position paper.
Preparation
Attendees are asked to submit a position paper about the Performance Pattern Language. I appreciate thoughts about expected usage and benefits of this language, intended audience and scope, related work, potential taxonomy, global forces, and everything I did not think about yet. Please do not write more than one or two pages.
Additionally all attendees are required to submit some Performance Patterns thumbnails. Each thumbnail should indicate in which domain(s) the pattern has been applied successfully.
What we will do
None of us has much experience with a Pattern Language Design Fest, so we have to find our way ourselves. At the beginning of the first session we will walk through the position papers, ask questions about them, and clarify our expectations. A first look at the prepared thumbnails will show for which domains these are applied, or could be applied. This will lead to a first version of an ordering schema or taxonomy.
During the actual Design Fest we need to cover the following roles:
Results
At the end of the Performance Patterns sessions, we will have identified the different domains where Performance Patterns can be applied, found some patterns for each domain, and identified some similarities in different domains. We will also have come up with an ordering schema of a rudimentary pattern language, where the discovered pattern fit in and where missing pattern and future work can be identified. Some actual pattern will be sketched.
After the Design Fest, we will collect the results and publish them in the conference proceedings.
Submission
Please send your position paper to me <pattern@kmarquardt.de> before June 15th, 2001. The Design Fest will most likely become a success when we find a balance between different technical domains, and the participants' strengths. Please indicate which domains you are familiar with, and which roles you'd prefer to play.