See http://2015.splashcon.org/track/plop2015#Bootcamp

See http://2015.splashcon.org/track/plop2015#Bootcamp

See http://2015.splashcon.org/track/plop2015#Bootcamp

See http://2015.splashcon.org/track/plop2015#Bootcamp

As organizations transition to agile processes, Quality Assurance (QA) activities and roles need to evolve. Traditionally, QA activities occur late in the process, after the software is fully functioning. As a consequence, QA departments have been quality gatekeepers rather than actively engaged in the ongoing development and delivery of quality software. Agile teams incrementally deliver working software. Incremental delivery provides an opportunity to engage in QA activities much earlier, ensuring that both functionality and important system qualities are addressed just in time, rather than too late. Agile teams embrace a whole team approach. Even though special skills may be required to perform certain development and Quality Assurance tasks, everyone on the team is focused on the delivery of quality software. The patterns in this paper are focused on identifying core qualities and prioritizing them on the project roadmap. Additionally during the process it is important to keep these qualities visible to the team and organization. Note to PLoP PC and potential shepherds: this is still preliminary work and submitted as a placeholder for evolution.

With increasing applications of design patterns and their variations for development of software applications, the accurate recovery of patterns from existing applications remained active research area in the last decade. The variations in standard patterns hamper accuracy of pattern recovery techniques and tools. There is no standard catalogue on all variants of Gang of Four(GoF) design patterns in literature. We present a catalogue on variations of GoF design patterns in this paper which are discussed in different publications, venues and forums at different levels of abstraction. The presented catalogue with 100 plus variants of standard patterns will serve as a knowledgebase for the design pattern research community and it may be used to specify GoF patterns and their variants. We evaluated three state of the art design patterns recovery tools on variants of selected design patterns and realize that state of the art tools are not capable to recognize all variants of GoF patterns. The critical analysis and observations on GoF design patterns and their variants are presented based on the whole study and our experience.

The architecture design during an agile project is an activity that should take place in all phases of a project lifecycle. Even given an initial architectural for a project, it is important to continue to evolve the architecture in order to keep it suitable for the applications current needs. This paper documents some patterns for working on and continue to evolve the architecture while using agile techniques.

By using Adaptive Object Models (AOM) it is possible to have a more flexible domain structure in an application, allowing its adaptation at runtime. Patterns for AOMs create a class structure completely different from the static structure that applications and frameworks are used to handle. As a result, AOM applications are not able to reuse existing frameworks, even the industry standards, which are meant for a static domain model. The Adapter pattern could be used to adapt the AOM structure for the one expected by the framework, however this adapter would need to be manually modified in every change on the AOM structure. This paper proposes a solution to this problem by creating a dynamically generated adapter for the current AOM structure. To exemplify the use of this approach, an implementation was created to adapt the AOM structure from the framework Esfinge AOM to the Java Beans API. Additionally, a framework for instance comparison based on the Java Beans specification was used to compare the adapted AOM entities.

Both patterns and reference architectures aim to describe solutions to be reused for development of software systems. Despite they have a common goal, they have a lot of differences and have also been investigated separately. The objective of this paper is to discuss the relationship between these two artifacts, and how they can be complementary, respecting their respective peculiarities. We also discuss how patterns can support the creation of reference architectures and how reference architectures can be source for pattern mining.

There have been a large amount of publications on the subject of logical layering in software architecture. What is rarely discussed is the manner how a software architect can design a layering model that satisfies the requirements of the system. In this work we present a software architecture patterns that defines the steps that need to be taken by a software architect to design a software architecture layering model that satisfies the given requirements: LOGICAL LAYERING HEURISTIC.

Christopher Alexander tells us, “Patterns must not be etched in stone; rather, they must grow as the users gain new experiences.” As co-author of the Fearless Change pattern language, Mary Lynn has steadily worked on this language with Linda Rising for almost 20 years. She will share her insights on keeping a pattern language alive and updated with changes to existing patterns and additions of new patterns. To do this, she will use the patterns in Fearless Change to explain how other authors can use these tools to keep their patterns growing and evolving, rather than being “etched in stone”.

Mary Lynn Manns

University of North Carolina Asheville, USA

United States

Dr. Manns received the Distinguished Teaching Award in the Sciences (1995), the Alumni Distinguished Faculty Award (2013), the University Service Award (2013), and the Feldman Professorship Award for Outstanding Scholarship and Service (2015). Her book, Fearless Change: Patterns for introducing New Ideas was featured as the “Best Book of the Year for 2004” in the Journal of Object Technology and made the “Books that Changed My Career” list on Amazon.com. In addition, her book was recently translated and published in Japanese and Chinese. She has published in peer reviewed journals and conference proceedings and is a primary editor on her second book, Pedagogical Patterns: Advice for Educators. She has done numerous professional presentations throughout the United States, Europe and South America at a variety of conferences and in organizations that include Microsoft, amazon.com, Avon, and Proctor & Gamble. Her research interest is in the area of change leadership. Dr. Manns’ newest book, More Fearless Change: Strategies for Making Your Ideas Happen, is now available.

Dr. Manns was the UNC Asheville commencement speaker in December 2013. Her speech about “changing the world” changed the world of graduation by including a little Zumba dancing– it begins at minute marker 27:15 here: https://www.youtube.com/watch?v=E7MhyZymTRM

This is your time to use the Fearless Change patterns to plan how you would like to make the world a better place. You can even use these patterns to improve yourself too. Bring your challenges and frustrations and those goals you haven’t yet found a way to start. You’ll get the opportunity to “play” with the patterns to begin your journey in becoming a leader of change!

Mary Lynn Manns

University of North Carolina Asheville, USA

United States

Dr. Manns received the Distinguished Teaching Award in the Sciences (1995), the Alumni Distinguished Faculty Award (2013), the University Service Award (2013), and the Feldman Professorship Award for Outstanding Scholarship and Service (2015). Her book, Fearless Change: Patterns for introducing New Ideas was featured as the “Best Book of the Year for 2004” in the Journal of Object Technology and made the “Books that Changed My Career” list on Amazon.com. In addition, her book was recently translated and published in Japanese and Chinese. She has published in peer reviewed journals and conference proceedings and is a primary editor on her second book, Pedagogical Patterns: Advice for Educators. She has done numerous professional presentations throughout the United States, Europe and South America at a variety of conferences and in organizations that include Microsoft, amazon.com, Avon, and Proctor & Gamble. Her research interest is in the area of change leadership. Dr. Manns’ newest book, More Fearless Change: Strategies for Making Your Ideas Happen, is now available.

Dr. Manns was the UNC Asheville commencement speaker in December 2013. Her speech about “changing the world” changed the world of graduation by including a little Zumba dancing– it begins at minute marker 27:15 here: https://www.youtube.com/watch?v=E7MhyZymTRM

Layering is hard. Patterns around layering have been created (e.g. shearing layers and layer pattern itself) and many books describe layering. But there is a lack of a pattern language in this field that can help architects to design a better layering. In our paper “Logical Layering Heuristic” (submitted to PLoP’15) we propose a method that provides a structured approach for coming to a good layering. However, behind this method (or high-level pattern) there certainly are hiding some patterns that, we believe, are the reasons for why the method is useful. The goal of this focus group is to identify both already described patterns and possible pattern candidates in the method (and in the good application of layering itself) as a first step towards a pattern language for layering. The focus hereby is holistic, we’re interested in ALL possibly relevant aspects of layering, incl. architectural/design patterns, organizational patterns, collaboration patterns, requirements patterns etc., and their relations.

Goals include, but are not limited to… a) Discover existing patterns that can be used in this pattern language; b) Pinpoint candidate patterns that can be expanded upon in new patterns descriptions.

Main discussion topics: a) What existing patterns can be included in the pattern language? b) What are new patterns that should be part of this language?

Participants should have experience with the application of layering in software architectures. It also would be good if they have read the paper “Logical Layering Heuristic”. A link to the article will be provided before the conference.

Pattern authors often struggle to find relevant design patterns across many sources ranging from books, papers, conferences, journals, and online repositories. Many attempts to build a central consolidated design pattern repository failed. Some possible explanations include: (a) pattern authors disagree on pattern formats to support; (b) a central repository raises thorny questions about design pattern ownership and attribution; (c) such a large and ambitious repository requires broad community support. In this workshop, an open, collaborative pattern repository is discussed as a possible solution to address previous challenges. We seek to understand the challenges and opportunities from a PLoP point of view.

The workshop is intended for design pattern authors and users. Its main goal is to introduce the open, collaborative design pattern repository and will involve a short presentation of the facilitators’ work, followed by an interactive discussion with the participants. Feedback from the participants can help to further refine the repository’s framework and identify different strategies that can encourage stakeholders to contribute and collaborate in building the repository.

Writer’s Workshop (WW) is a method to review, evaluate and improve each other’s pattern, which is widely accepted in xPLoP conference including this EuroPLoP. However, there are several problem existing in traditional WW such as “poor experience of moderator”, “poor knowledge of participants” or “poor pattern accepted”. Detail discussion of these problem could be found in our work. As a solution to these “ad hoc” reviewing, we suggest utilizing some software reading techniques such as Checklist-Based Reading (CBR) or Perspective-Based Reading (PBR) into WW. In this focus group, we are going to discuss it together by conducting a mini WW.

Key Idea: We have conducted experiments in this topic several times before. Based on those result, we will hold this focus group in the idea of “Customized checklist” and “Using checklist as a remainder”. Thus to say, participants will receive checklists made for reviewing target paper, and keep the contents in mind during reading and discussion, as a remainder. Detail process could be found in this paper.

Target participants: We prefer to have newer author join us, as we believe that our approach will have much effect on them. Of course, experts are also welcomed. We are willing to listen to your opinion on this approach and discuss together.

Joe Yoder

The Refactory, Inc.

United States

Rebecca Wirfs-Brock

Wirfs-Brock Associates

Is “software engineering” really engineering yet? The term was coined in 1968 to call attention to problems with software production. Both theory and practice for software have evolved since then, but do we by now have a true engineering discipline? Classical engineering disciplines have emerged from craft practice and commercialization through the infusion of codified knowledge and science. Using this emergence pattern as a point of reference, I will sketch the evolution of software engineering, drawing on civil engineering and software architecture for examples that show the progressive codification of informal knowledge toward rigorous models and tools. This will provide the basis for assessing the maturity of the field and identifying our next challenges.

Mary Shaw

Carnegie Mellon University

A recent paper did an experiment to show that security patterns are not very useful. However, they did not consider methodologies, only patterns in isolation. This group will intend to discuss the following questions relevant to the use of security patterns:

1. Do we have good methodologies to build secure systems using patterns? If so, why are they not used?
2. Can we merge or combine some of them to have a complete (with tools) and tested methodology?
3. Can we have a unified catalog? At least, unified pattern descriptions. We started to work in this direction in EuroPLoP.

I think there is plenty to talk about these topics but I will accept suggestions for other relevant questions. The idea is for researchers on security patterns to exchange ideas and start possible collaborations.

Software engineering research follows a variety of paradigms, including empirical studies, formal analysis, system building, systematic literature review, and qualitative studies. Unfortunately, the field has generally not been very explicit about how research in these styles should be reported, especially about the differences between reports of research in different styles. The problem lies not just in the surface qualities of the papers, but in the deep structure – the scientific arguments. Careful reading of good papers reveals considerable regularity. This calls out for a pattern language that captures the recurring elements: identifying the settings where they are appropriate, the ground rules for carrying them out, and suitable ways to use them in combination.

The bare bones of such a Pattern Language for Software Engineering Research Papers are under development at SEresearchpatterns.org. There are patterns that capture the structure of the scientific argument and the way it maps to the overall structure of the paper. There are patterns for elements within papers (e.g., traceability from claim to result, related work) that are used in numerous types of papers. To get started, it focuses on 8-10 page conference papers.

The goal of this focus group is to put some meat on those bare bones. That means identifying patterns for more paradigms, recognizing commonalities and differences, and refining the levels of granularity in the language. We will try to capture the essence of the resulting patterns but probably will not have time to write them in detail.

It would be very helpful if participants would choose three or four papers in their preferred research style and sketch the patterns that they find in the style of http://SEresearchpatterns.org.

Mary Shaw

Carnegie Mellon University

Pattern Writers Workshop (WW) is a method to review and improve each others pattern or pattern language papers there could be several problems leading to ad hoc review meetings. Software reading techniques, Checklist-Based Reading (CBR) and Perspective-Based Reading (PBR) is considered as a solution to it in previous research. In this paper, we propose an approach to improve it by providing a two-level checklist and refined perspectives. Moreover, by conducting some experiments, we discuss the effectiveness and drawbacks of this approach.

We present a threat pattern that describes attacks against applications vulnerable to cross-site scripting (XSS). This pattern provides insight on how to build and configure secure applications and is also helpful in evaluating the security of existing applications. Cross-Site Scripting is listed as number three risk on the 2013 OWASP Top 10 list; it is an attack, which is made possible due to the lack of user input validation or output escaping.

Money is so prevalent in our lives that we often don’t think about its content or implementation from a computer science perspective. Two of the most popular platforms (Java and .NET) either do offer Money API (Oracle plans to introduce Money API in its upcoming Java SE 9 release [1]) or have a limited API within a specific part of their framework (Microsoft .NET only offers Money API as part of their Dynamics CRM 2015 Microsoft.Xrm.Sdk Namespace [3]). Interestingly, even Microsoft did not introduce the Money API until 2011. In Java, Currency API has been been introduced in Java SE 1.4 (the latest version currently offered by Oracle is Java SE 8) [2]. With continuous and rapidly expending internationalization of enterprise applications, there is an ever increasing need to have access to reusable and extensible implementation of the Extended Money Object and Money API.

Pattern language were invented by architect Christopher Alexander as a way to scribe out what he called the Quality Without a Name (QWAN) which causes the beautiful traits of towns and buildings to occur. Architecture with the QWAN is said to have wholeness which is created by centers that intensify one another. Alexander defines the 15 Fundamental Properties to show the way these centers interact with one another. In according to this, Alexander redefined patterns to be a method to make these 15 properties to occur in life. However, these 15 properties are geometrical properties which its effectiveness is limited to only physical objects. Accordingly, these properties are not compatible with pattern languages that are categorized as the Pattern Language 3.0 group of patterns which deal with non-tangible human actions. We hypothesized that there must be another set of fundamental properties that deal with these patterns of non-tangible human actions, and created the 24 Fundamental Behavioral Properties (Iba, et al., 2015a). This is part two of the series of papers which describe these properties in detail. It succeeds our paper presented in EuroPLoP 2015 which introduced 6 properties (Iba et al., 2015c), and will introduce another 9 more properties (ACCOMPANY, EMPATHY, ENHANCING, BUILDING UP, REFLECTING, GROWTH, AIMING, CONTRAST, CONTINUATION). By opening up the discussion on these properties with the patterns community we hope for these to become knowledge to help all who are writing and will write patterns for human actions to make their patterns full of life.

‘Starting from Contact’ is a process for a company to collaborate with local community on social issues. Starting from Contact is a process that starts from building relationships among members who have gathered together based on common interests rather than picking team members based on required functions. And then, people gather and come up with an issue in common for starting a project. For the past 4 years, Starting from Contact process have been tried and tested in Tohoku, Japan and there were some core ideas shared and repeated among 10 members of Fuji Xerox, which we would like to share in this paper as patterns. We believe Starting from Contact process could be a powerful process to involve both company members from outside the community and local members inside the community. We believe it can lead to collaboration in thinking and acting on social issues in a positive inner motivational driven way.

Security patterns (SPs) are reusable solutions to security problems. We study here research papers that use security patterns to build secure systems or analyze the nature of security patterns. The goal of this paper is neither listing nor direct mapping of existing over 200 SPs but finding about how SPs are being investigated within research works to guide future research targeting SPs. Although the number of SPs has recently grown, two critical problems remain due to the diversity in the results themselves and how they are shared. First, it is unclear whether or not the field is actively growing. Second, the trends in SP research (e.g., research content and their modeling methods of SPs) are uncertain. To elucidate the current trends, herein we classify 30 works on SPs using a technique called systematic mapping (SM), which reveals the following characteristics. As the frequency of less common patterns (e.g., reference monitor) increases, the amount of practical research (e.g., experimental evaluations) also increases; Regardless of SPs to be dealt with, the most common SP modeling method is UML followed by other modeling methods for specific purposes, demonstrating the importance of modeling methods complementing each other; Currently one the most common research topics is applying SPs, suggesting that the demand for efficient and reliable techniques to applying SPs is high; Future studies should examine other SPs in addition to access control to handle various threats as well as to investigate the analysis/requirement and test phases; Accumulated knowledge on SPs should improve research requiring precise modeling.

A major difficulty of system development is the initial understanding of the customers’ business, their needs, and their expectations as well as the correct specification of this information in requirements during the project proposal stage. This paper presents the \textit{Executive Proposal}, a pattern of sequenced stages of processes, used to assist communication between the supplier and the customer organizations during the preparation of the proposals of software projects. This pattern aims to facilitate the capture of the initial project requirements and the validation of the software projects’ proposals by the customer.

The software business is directing its growth towards service-oriented businesses models, highly supported by cloud computing. While cloud computing is not a new research subject, there’s a clear lack of documented best practices to orchestrate both public and private cloud environments. This paper describes existing solutions for cloud orchestration by introducing them as three patterns: I) Isolation by Containerization, providing resource sharing with minimal virtualization overhead, II) Orchestration by Resource Offering, ensuring orchestration places the application in a machine with the resources to run it and III) Discovery by Local Reverse Proxy, allowing applications to access any service in a cluster abstracting its exact address. The authors believe these three DevOps patterns will help newcomers to cloud orchestration to adopt best practices earlier, hence, improving their software life cycle management.

The nature of in-class meetings in a Flipped Classroom setting is certainly different from traditional lectures. Most often the time is used for providing feedback to the students, helping them with correcting misconceptions and providing support for deeper learning. One often applied way is the usage of student solutions as starting point for giving feedback and other teaching activities, which is also described in the pattern USE STUDENT SOLUTIONS. This paper proposes five patterns that help with using the student solutions in an effective way, hereby also taking the aspects of motivation and respect into account.

Startups are human organizations focused on innovation, generally, under lack of resources. Then, a highly uncertain environment is created that influences how software is developed. This set of patterns tries to capture the expertise found in literature to help founders and employee developers to optimize software development process under the unique circumstances that a startup faces. We present seven new patterns: Be Agile, Use Open Source Solutions, Simple Tools, Early Validation, Empower, In the clouds and Celebrate failure and discuss the relations between them and other patterns already presented in literature.

Online learning systems are complex systems that are frequently updated with new content, upgraded to support new features and extended to support new technologies. Maintaining the quality of the system as it changes is a challenge that needs to be addressed. Design patterns offer a solution to this challenge by providing guides to stakeholders responsible for making design changes (e.g., system developers, HCI designers, teachers, students) that will help them ensure system quality despite changes. Although design patterns for online learning systems exist, they often focus on one aspect of the system (e.g., pedagogy, learning). The data-driven design pattern production (3D2P) methodology utilizes data for producing design patterns in collaboration with stakeholders, addresses stakeholders concerns, and ensures the systems quality as a whole. The paper presents five patterns produced by applying the methodology on the ASSISTments online learning system namely: all content in one place, just enough practice, personalized problems, worked examples, and consistent language. We made two changes to the pattern format: added in-text references in the forces section, and added an evidence section. The references allow the reader to learn more about the force in question. The evidence section highlights key findings uncovered from the 3D2P methodology. Four sources of evidence were considered in the pattern format: (a) literature existing research on the problem or solution, (b) discussion expert opinions about the problem or solution, (c) data measures of the problems recurrence, and the solutions effectiveness based on collected data; and (d) evaluation assessment of the patterns performance when it was applied on an existing system. The changes to the format highlight linkages between pattern elements, theory, and empirical evidence. We believe that links further justify the design pattern, and make it easier for multiple stakeholders to understand them.

In this paper, we address the method and practice of continuously creating pattern language before, during, and after the process of shaping the campus, as an agile design method involving the campus users. The process of creating pattern language that grasps discoveries and findings in campus planning is disclosing and enables all the users to pursue their ideal campus. The patterns that were shaped can be categorized in three domains; architecture and landscape, educational programs, and internal activities for campus planning. This paper also adopts the practical example of the campus planning process of a residential education and research facility, called Student Build Campus, an initiative that allows people to create their own campus at Keio University, Shonan Fujisawa Campus in Japan. Our research is based on architect Christopher Alexanders studies on the Oregon Experiment and the construction of Eishin Gakuen Higashino High School. We also present the point in which the process of creating pattern language follows the research studies from the agile design method developed in the field of software design.

This will become a high-level pattern language on innovating and finding new ideas. Each pattern will be very brief (1-2 pages), in order to provide a quick entry into the world of innovation. As the patterns are high level, there are certainly many more specific patterns that can be discussed in future papers. Creativity and lateral thinking are key skills in almost every domain. They are required to innovate, develop new ideas, get deeper insights, address challenges and resolve conflicts. In this context we understand creativity as the process of creating and developing new and original ideas as one step in the innovation process.

This paper is a challenge to clear the importance and specific theory of drawing illustrations for pattern language. In this paper we introduce Pattern Illustration as visual expressions on pattern language for human action, like education, organizational design and so on. In order to draw better illustration, we present 6 patterns of all 28 patterns in Pattern Illustration Patterns, which are No.0 Pattern Illustration, No.1 Essential Message, No.2 Moving Characters, No.3 Symbolic Representation, No.4 Center Words Hunting, and No.13 Lively Peak Capture.

The possibility of patterns begins in Alexanders first book (1964), Notes on the Synthesis of Form (Notes), with the idea of the diagrams. However, patterns as later presented (1977) in A Pattern Language (APL) and thereafter commonly understood, differ in important ways from those in Notes. This paper discusses those differences in the context of the self-conscious and un-self-conscious processes discussed in Notes and surmises that large bodies of undiscovered patterns await exploration. Why these untouched patterns are potentially critical provides the conclusion to the paper.

Important aspects of assessments in education are that they are fair and relevant for the targeted learning outcomes. Patterns as descriptions of tested ways can help university teachers with reaching these goals, as these teachers are often not trained in these specific aspects of education. The patterns on fair assessments presented in this paper have been mined by a group of practicing educators during the first EduPLoP. They build on the foundational assessment patterns and address aspects such as transparency on what and how will be assessed and respecting the diversity of the student population.

We present here a pattern for a Software Container. A Software Container provides an execution environment for applications sharing a host operating system, binaries, and libraries with other containers with strong isolation between them. Software containers although not new, have become very important to support convenient, secure, and low-overhead applications.

This pattern language describes different strategies to build an innovative startup. We propose patterns for the different problems that a startup has to deal with. While some patterns are more related to technical issues, other focus on human and management aspects of new, creative companies. The pattern language can be used as a set of tools for high-tech entrepreneurs.

We describe nine design patterns that we have developed in our work on the Peeragogy project, in which we aim to help design the future of education along the principles of free/libre/open source software. We use these patterns to build an ‘emergent roadmap’ for the project. Our use of design patterns has some novel features that will be relevant to others working in projects with emergent structure.

Businesses constantly consume, generate and share data. Without data, a typical business process would come to a halt. But for the data to be useful to businesses, it must be accessible, manageable, current, and it must be auditable. Because enterprise applications are designed for multi user environments, the audit trail of any data creation, update, and deletion is of paramount importance. Users (and processes) should not be allowed to change business data without some sort of audit trail tied to the said change. Furthermore, often changes require approvals, validations and verifications, which could take time. Thus the proposed changes cannot be performed on the original set of data, but must rather be done on a copy of that data. This approach allows for the existing data to be available within a system which the proposed changes are being approved, validated and verified. Furthermore, should the proposed changes be rejected, the original data stays intact. In this paper we propose a Business Data Object Versioning and Change History Pattern, which we hope will be useful when designing enterprise applications which require adherence to legal and corporate audit record creation and maintenance.

Design patterns are supposed to be the well documented, tried and tested solutions to recurrent problems. Current evaluation techniques do not provide a demonstrable and holistic means to evaluate the quality of the pattern presented. This paper introduces Pattern Report Cards an evaluation process for software design patterns that is demonstrable, measurable, and reproducible. We have identified a set of quality indicators for determining pattern quality, and assembled a set of qualitative and quantitative evaluation techniques to determine how well a given pattern adheres to these indicators. Further, management and execution of the evaluation process is controlled by the PREMES framework. This framework describes a management cycle that facilitates the construction of bespoke evaluation systems for design patterns. Tailoring of the process is achieved by providing guidance over the selection and construction of the techniques used to assess pattern quality. Use of these techniques will help bolster existing evaluation processes and lead to the improvement evaluation techniques for design patterns.

60 years ago German, U.S. American and Swiss psychotherapist Ruth C. Cohn started to develop Theme-Centered Interaction as a framework to humanely facilitate educational groups. Today it is well-known in Europe and India, but not in the U.S. The author of this paper believes that Ruth C. Cohn actually wrote a pattern language, therefore he reproduces Cohn’s basic ideas in patterns form. Ruth C. Cohn’s work is an important and useful toolset for facilitating groups. So the goal of this paper is to re-introduce her work among an international audience. The work perfectly complements the existing body of facilitation patterns.

Parallel computing architectures have been proven to significantly boost performance and are, therefore, being increasingly adopted in industrial applications. However, our experience with applications built on parallel computing architectures reveals that often they are not designed properly to leverage the power of these architectures and consequently suffer from performance ‘‘smells’’. We believe that an awareness of such smells can help practitioners design better and faster applications. However, our study of the existing literature on performance smells reveals the lack of a generalized comprehensive smell catalog that focuses on parallel computing. To address this gap, we have aggregated and cataloged commonly-occurring performance smells related to parallel computing. In this paper, we describe these smells along with their associated mitigation techniques, and attempt to draw out the relationships between different smells.

Students learn more when they are actively involved during lectures. In earlier work we presented patterns that help with making lectures more interactive. In this paper we present three additional patterns and embed them in the overall collection of lecture design patterns with the goal of forming a pattern language that helps educators with improving their lectures.

A design pattern is generally understood as both a simplifying ideal for solving a recurrent problem, like having a receptionist for a crowded gathering, doing research on how to treat foreign guests, or upgrading whole systems rather than parts sometimes. They simplify the solution by satisfying all the key needs at once. Varying examples of how to satisfy these common problems may be found by looking in other places for the most general design pattern they fit, perhaps called: orientation, introduction and life-cycling. Finding a variety of living examples to study and learn from introduced to the intricacies and variation of living examples, and their sources of elusive features like living quality . A design pattern used this way really becomes more of a reference manual, linked to all the places the recurrent problem arises. Seen that way, design patterns are not really instruction sets but guides, opening the door to getting guidance from the naturally occurring variations on common design patterns. The practical examples to be discussed demonstrate how to use a model design pattern meant for one circumstance, to search for related natural design patterns in other places. It builds a deeper understanding of 1) the model pattern and its potential features and roles, 2) the artful complexity of natural designs , and 3) their sources of living quality. The model pattern might be called vehicle perhaps, and you might study various instances where versions of vehicle occur naturally as a life pattern, to see what they have to teach you.