Team Situational Awareness and Architectural Decision Making with the Software Architecture Warehouse

The core of the design of software architecture is all about architectural decision making. A high-quality design outcome sets high requirements, not only on the skills and knowledge of the design team members, but also on the management of the decision making process. We claim that in order to deliver high quality decisions, the design team needs to obtain a high level of situational awareness. To address this, we present an analysis of the problem of team situational awareness in design workshops and propose a model on how stakeholder positions help to build consensus within the argumentation viewpoint of architectural decisions. We show how the Software Architecture Warehouse tool has been extended to support the argumentation viewpoint within its live design document metaphor to provide support for co-located and distributed design workshops.

[1]  Paris Avgeriou,et al.  Forces on Architecture Decisions - A Viewpoint , 2012, 2012 Joint Working IEEE/IFIP Conference on Software Architecture and European Conference on Software Architecture.

[2]  Frank Leymann,et al.  Managing architectural decision models with dependency relations, integrity constraints, and production rules , 2009, J. Syst. Softw..

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

[4]  Bashar Nuseibeh,et al.  Weaving Together Requirements and Architectures , 2001, Computer.

[5]  Cesare Pautasso,et al.  Architectural decision modeling with reuse: challenges and opportunities , 2010, SHARK '10.

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

[7]  Peng Liang,et al.  Architectural design decision: Existing models and tools , 2009, 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture.

[8]  Torgeir Dingsøyr,et al.  Introduction to Software Architecture and Knowledge Management , 2009, Software Architecture Knowledge Management.

[9]  Mica R. Endsley,et al.  Theoretical Underpinnings of Situation Awareness, A Critical Review , 2000 .

[10]  Daniel J. Garland,et al.  Situation Awareness Analysis and Measurement , 2009 .

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

[12]  .. V. Heescha,et al.  The Journal of Systems and Software , 2022 .

[13]  Rick Kazman,et al.  Decision-making techniques for software architecture design: A comparative survey , 2011, CSUR.

[14]  Uday S. Murthy,et al.  Divergent and Convergent Idea Generation in Teams: A Comparison of Computer-Mediated and Face-to-Face Communication , 2004 .

[15]  Michael Wing Roller coaster , 2006, SOEN.

[16]  Heiko Koziolek,et al.  An industrial case study of performance and cost design space exploration , 2012, ICPE '12.

[17]  Muhammad Ali Babar,et al.  Software Architecture Knowledge Management: Theory and Practice , 2009 .

[18]  Gary Klein Sources of Power , 1998 .

[19]  Muhammad Ali Babar,et al.  A Tool for Managing Software Architecture Knowledge , 2007, Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007).

[20]  M. S. Poole,et al.  Communication and Group Decision-Making , 1986 .

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

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

[23]  I. Gorton,et al.  A quality-driven systematic approach for architecting distributed software applications , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..