Leveraging Architecture Patterns to Satisfy Quality Attributes

Architectural design has been characterized as making a series of decisions that have system-wide impact. These decisions have side effects which can have significant impact on the system. However, the impact may be first understood much later; when the system architecture is difficult to change. Architecture patterns can help architects understand the impact of the architectural decisions at the time these decisions are made, because patterns contain information about consequences and context of the pattern usage. However, this information has been of limited use because it is not presented consistently or systematically. We discuss the current limitations of patterns on evaluating their impact on quality attributes, and propose integrating the information of patterns' impact on quality attributes in order to increase the usefulness of architecture patterns.

[1]  Uwe Zdun,et al.  Architectural Patterns Revisited - A Pattern Language , 2005, EuroPLoP.

[2]  Mark Klein,et al.  Attribute-Based Architectural Styles , 1999 .

[3]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[4]  Mary Shaw,et al.  Software architecture - perspectives on an emerging discipline , 1996 .

[5]  Jan Bosch,et al.  Software Architecture: The Next Step , 2004, EWSA.

[6]  Leonard J. Bass,et al.  Risk Themes Discovered through Architecture Evaluations , 2007, 2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07).

[7]  David Garlan,et al.  Software architecture: a roadmap , 2000, ICSE '00.

[8]  Philippe Kruchten,et al.  The Rational Unified Process: An Introduction , 1998 .

[9]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[10]  KruchtenPhilippe The 4+1 View Model of Architecture , 1995 .

[11]  B. J. Ferro Castro,et al.  Pattern-Oriented Software Architecture: A System of Patterns , 2009 .

[12]  Jan Bosch,et al.  Software Architecture as a Set of Architectural Design Decisions , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[13]  Robert L. Nord,et al.  Generalizing a Model of Software Architecture Design from Five Industrial Approaches , 2005, 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05).

[14]  Jeff Tyree,et al.  Architecture decisions: demystifying architecture , 2005, IEEE Software.

[15]  Uwe Zdun,et al.  Using Patterns to Capture Architectural Decisions , 2007, IEEE Software.

[16]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[17]  Philippe Kruchten,et al.  Building Up and Reasoning About Architectural Knowledge , 2006, QoSA.

[18]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[19]  Leonard J. Bass,et al.  Designing software architectures to achieve quality attribute requirements , 2005, IEE Proc. Softw..

[20]  Robert L. Nord,et al.  A general model of software architecture design derived from five industrial approaches , 2007, J. Syst. Softw..

[21]  B. F. Castro Buschmann, Frank; Meunier, Regine; Rohnert, Hans; Sommerlad, Peter; Stal, Michael. Pattern-oriented software architecture: a system of patterns, John Wiley & Sons Ltd, 1996 , 1997 .

[22]  Alexander L. Wolf,et al.  Software architecture , 2001 .

[23]  Robert L. Nord,et al.  Applied Software Architecture , 1999, Addison Wesley object technology series.

[24]  Ilene Burnstein,et al.  Practical Software Testing: A Process-Oriented Approach , 2003 .

[25]  Ilene Burnstein,et al.  Practical Software Testing , 2003, Springer Professional Computing.

[26]  P. Krutchen,et al.  The Rational Unified Process: An Introduction , 2000 .