;As software increases in size and becomes more complex and costly, the need for techniques to ease software development is likewise increasing. Over the last decade, pattern community has evolved and received more interest in both academia and industry. Developing software using patterns holds the promise to reduce the cost and condensing the time of developing software systems, while simultaneously maintaining the quality of these systems.
However, the potential of using patterns in developing systems is not fully realized and many challenges are need to be addressed. For example, developing pattern repositories and catalogs, from which patterns can be retrieved and reused, still forms a challenge to software engineering, knowledge engineering and information systems communities. In addition, the need for (semi-)automated approaches for patterns mining and integration poses several open research question to software engineering community. It is believed that these challenges and others preclude the realization of the benefit of patterns as a reuse approach. This workshop aims at bringing together researchers and parishioners who are interested in resolving research challenges or who have practical experience with the different issues of patterns reuse and integration to discuss and advance the state-of-the-art and the state-of-the-practice in patterns reuse.
This workshop will examine how to compose any system as a system of patterns with respect to four central themes:
1. How does one select analysis and design patterns to build any system?
2. What is the base for selecting these patterns?
3. How does one integrate the selected patterns to build any system?
4. What is the impact of software stability on systems using patterns?
The workshop will debate several issues related to the question: how does one compose any system from patterns. We want researchers, framework developers, and application developers to answer the following questions:
1. Are the various claims related to building any system from patterns reasonable?
2. What do we mean when we say "systems of patterns"?
3. What are the various claims related to patterns composition; are they true?
4. If someone would like to build a system from patterns, how do you select patterns?
5. What kind of patterns should one select to build a system from patterns?
6. Is there a guideline for the selection process?
7. How does one select analysis and design patterns to build such systems?
8. How does one compose patterns?
9. Are there any guidelines for patterns composition?
10. What other concepts will help build any system from patterns?
11. What is the impact of the software stability model [fayad] on building any system from patterns?
