A Survey of Architectural Design Decision Models and Tools

In the field of software architecture, there has been a paradigm shift from describing the outcome of architecting process mostly described by component and connector (know-what) to documenting architectural design decisions and their rationale (know-how) which leads to the production of an architecture. This paradigm shift results in emergence of various models and related tools for capturing, managing and sharing architectural design decisions and their rationale explicitly. This report intends to make a survey about the well-known existing architectural design decision models and their related tools.

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

[2]  Patricia Lago,et al.  Architectural Knowledge: Getting to the Core , 2007, QoSA.

[3]  Peng Liang,et al.  Knowledge Architect: A Tool Suite for Managing Software Architecture Knowledge , 2009 .

[4]  Peng Liang,et al.  Refinement to Griffin Core Model and Model Mapping for Architectural Knowledge Sharing , 2007 .

[5]  Remco C. de Boer,et al.  In search of `architectural knowledge' , 2008, SHARK '08.

[6]  Frank Leymann,et al.  Architectural Decision Models as Micro-Methodology for Service-Oriented Analysis and Design , 2007 .

[7]  Philippe Kruchten,et al.  An Ontology of Architectural Design Decisions in Software-Intensive Systems , 2004 .

[8]  Philippe Kruchten,et al.  Visualizing Software Architectural Design Decisions , 2008, ECSA.

[9]  V. Clerc,et al.  Structuring Software Architecture Project Memories , 2005 .

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

[11]  Rafael Capilla,et al.  Processes for Creating and Exploiting Architectural Design Decisions with Tool Support , 2007, ECSA.

[12]  Dieter K. Hammer,et al.  Tool Support for Architectural Decisions , 2007, 2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07).

[13]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[14]  Rafael Capilla,et al.  Modeling and Documenting the Evolution of Architectural Design Decisions , 2007, Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007).

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

[16]  P. Avgeriou,et al.  17 Collaborative Software Architecting through Knowledge Sharing , 2009 .

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

[18]  Rafael Capilla,et al.  A web-based tool for managing architectural design decisions , 2006, SOEN.

[19]  Frank Leymann,et al.  Reusable Architectural Decision Models for Enterprise Application Development , 2007, QoSA.

[20]  Philippe Kruchten,et al.  A Tool to Visualize Architectural Design Decisions , 2008, QoSA.

[21]  Patricia Lago,et al.  SOA process decisions: new challenges in architectural knowledge modeling , 2008, SHARK '08.

[22]  Jos Nijhuis,et al.  Design Decisions: The Bridge between Rationale and Architecture , 2006 .

[23]  Patricia Lago,et al.  Effective Tool Support for Architectural Knowledge Sharing , 2007, ECSA.

[24]  Frank Leymann,et al.  The Role of Architectural Decisions in Model-Driven SOA Construction , 2006 .

[25]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[26]  Antony Tang,et al.  A rationale-based architecture model for design traceability and reasoning , 2007, J. Syst. Softw..

[27]  Hans van Vliet,et al.  Software Architecture Design Reasoning , 2009, Software Architecture Knowledge Management.