Premium
Pattern languages: addressing the challenges
Author(s) -
Fayad Mohamed E.,
Singh Shivanshu K.
Publication year - 2013
Publication title -
software: practice and experience
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.437
H-Index - 70
eISSN - 1097-024X
pISSN - 0038-0644
DOI - 10.1002/spe.2205
Subject(s) - pattern language (formal languages) , computer science , software design pattern , architectural pattern , structural pattern , context (archaeology) , process (computing) , software development , theme (computing) , design pattern , field (mathematics) , software , software engineering , programming language , artificial intelligence , software design , world wide web , paleontology , mathematics , pure mathematics , biology
A pattern language usually consists of a cascade or hierarchy of parts, linked closely together by patterns, which solve generically recurring problems that are associated with these parts. Each pattern has a specific title, and collectively, these titles form a language for design [1]. Pattern languages are in life, simply, a collection of interrelated patterns [2]. These interrelated patterns combine in any way and means to create new environments, where practitioners can solve context-specific problems. To be precise, the concept of pattern languages has spilled over into the software engineering field, to describe prior experiences and those processes that stem from them, in a very simple and easy to understand language, where patterns are tactfully woven as a whole, and combined in any manner to solve a particular and complex problem. Yet, this process is ad hoc and is not straightforward enough to ease and speed up the software development process. Thus, three main issues carry forward this theme section. First, how can we classify, develop, design, and utilize analysis and design patterns together, following the path to a problem resolution? Second, what is the ‘behind-the-language’ that guides the sewing of patterns together as a whole? Third, how can we overcome and face challenges, other than pattern composition problems (patterns traceability, etc.) that can hinder the development of a system of patterns? An inherent inability to answer these questions is detrimental in understanding how to put patterns into real practice. The use of software patterns is therefore more complex than it should be in practice.