SEARCH

SEARCH BY CITATION

Building high-quality systems is not an easy exercise, specifically when several factors can undermine their quality success, such as cost, time, and lack of systematic approaches. The potential promise of using software patterns in software development to deal with these aforementioned obstacles has led software practitioners to steadfastly believe in the power of pattern languages, as the means for constructing complex systems in a constrained environment.

Software Patterns, along with Pattern Languages, have attracted software practitioners for more than a decade, being seen as promising techniques that ease and speed up software development. However, developing robust software patterns and pattern languages has not reached the expected levels of ease and flexibility, when dealing with complex problems; instead, they construct models that specifically lack some essential qualities that diminish the overall quality of the system rather than improving it.

The concept of Pattern Languages is spilling over into the software engineering field, to highlight software development's prior experiences or best practices, using a coherent language that can be used both for discussing a particular problem and also creating new environments from the patterns it conveys. This language works by connecting a collection of patterns, as if they were in a detailed, narrated story. Each of the patterns in the collection is an insightful and novel way to manage or solve a set of recurrent problems in a particular context. As a whole, they make clearly visible both the knowledge that is pertinent to a particular domain, and the solutions for a set of recurrent problems.

Pattern languages have emerged as a promising classification technique and as a means for building frameworks. However, there are many problems, including: (1) Missing indicators/guidelines for in-context pattern selection within the pattern language; (2) Absence of a classification structure for a patterns' rationale within the pattern language structure; (3) Loss of traceability, especially when dealing with deeper levels of pattern language implementation; (4) The lack of a systematic way for compositing these patterns, similar or different, to build software architectures; (5) A loss of generality in traditional pattern languages; (6) Struggles and conflicts in providing full software maintainability and stability to pattern languages; (7) Pattern languages are not easy to use; (8) There is no set classification in pattern languages; (9) There is no distinction between associate and remote knowledge in pattern languages.

Researchers, framework developers, and application developers are invited to contribute to the special issue. Topics include, but are not limited to, the following:

  • Pattern Languages Creation and Development

  • Pattern Languages Selection Process

  • Patterns Languages Composition

  • System of Patterns

  • General Reuse and Impacts.

Submission Details

  1. Top of page
  2. Submission Details

Prospective authors are kindly requested to submit their manuscripts using the Journal's online submission system, found at http://mc.manuscriptcentral.com/spe no later than 31 December 2010.

Please follow the instructions under ‘Author Guidelines’ on the Journal homepage http://wileyonlinelibrary.com/journal/softwarepractice. A link to the online submission system will also be found here.

When submitting your article to this Special Issue, make sure that you have selected the Article Type ‘Special Issue Article’ and in Editor Selection select ‘M. E. Fayad and Shivanshu Singh’. For the Special Issue title insert: ‘PLAC’.