The lonesome architect

Although the benefits are well-known and undisputed, sharing architectural knowledge is not something architects automatically do. In an attempt to better understand what architects really do and what kind of support they need for sharing knowledge, we have conducted large-scale survey research. The results of our study indicate that architects can be characterized as rather lonesome decision makers who mainly consume, but neglect documenting and actively sharing architectural knowledge. Acknowledging this nature of architects suggests ways to develop more effective support for architectural knowledge sharing.

[1]  Hans van Vliet,et al.  Understanding how to support architects in sharing knowledge , 2009, 2009 ICSE Workshop on Sharing and Reusing Architectural Knowledge.

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

[3]  Bradley R. Schmerl,et al.  The Radar Architecture for Personal Cognitive Assistance , 2007, Int. J. Softw. Eng. Knowl. Eng..

[4]  Peng Liang,et al.  Collaborative Software Architecting Through Knowledge Sharing , 2010, Collaborative Software Engineering.

[5]  Philippe Kruchten,et al.  The Software Architect -and the Software Architecture Team , 1999 .

[6]  Patricia Lago,et al.  Eagle: Effective Tool Support for Sharing Architectural Knowledge , 2007, Int. J. Cooperative Inf. Syst..

[7]  Leonard J. Bass,et al.  Evaluating the Software Architecture Competence of Organizations , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).

[8]  Patricia Lago,et al.  The Architect's Mindset , 2007, QoSA.

[9]  Philippe Kruchten,et al.  The Decision View's Role in Software Architecture Practice , 2009, IEEE Software.

[10]  Martin Fowler.  Design - Who needs an architect? , 2003, IEEE Software.

[11]  Paris Avgeriou,et al.  Tools and Technologies for Architecture Knowledge Management , 2009, Software Architecture Knowledge Management.

[12]  M. Huysman,et al.  Practices of managing knowledge sharing: towards a second wave of knowledge management , 2004 .

[13]  Shari Lawrence Pfleeger,et al.  Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..

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

[15]  Philippe Kruchten,et al.  What do software architects really do? , 2008, J. Syst. Softw..

[16]  Weiguo Fan,et al.  Tapping the power of text mining , 2006, CACM.

[17]  Kurt Schneider,et al.  Modeling and Improving Information Flows in the Development of Large Business Applications , 2009, Software Architecture Knowledge Management.

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

[19]  Philippe Kruchten,et al.  Architectural knowledge and rationale: issues, trends, challenges , 2007, SOEN.

[20]  Kathryn Cormican,et al.  Knowledge Sharing in a Collaborative Networked Environment , 2007, J. Inf. Knowl. Manag..

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

[22]  Patricia Lago,et al.  A Just-In-Time Architectural Knowledge Sharing Portal , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).

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

[24]  H. van Vliet,et al.  Experiences with a Wiki to Support Architectural Knowledge Sharing , 2008 .

[25]  Johan F. Hoorn,et al.  The lonesome architect , 2009, 2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture.

[26]  Johan F. Hoorn,et al.  Shifts in foci and priorities. Different relevance of requirements to changing goals yields conflicting prioritizations and is viewpoint-dependent , 2006, Softw. Process. Improv. Pract..

[27]  Mark Klein,et al.  The Duties, Skills, and Knowledge of Software Architects , 2007, 2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07).

[28]  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).

[29]  Remco C. de Boer,et al.  Knowledge Management in Software Architecture: State of the Art , 2009, Software Architecture Knowledge Management.

[30]  Paris Avgeriou,et al.  First workshop on sharing and reusing architectural knowledge , 2006, SOEN.

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

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

[33]  Hans van Vliet,et al.  Stakeholder Perception of Enterprise Architecture , 2008, ECSA.

[34]  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).

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

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

[37]  Shari Lawrence Pfleeger,et al.  Principles of survey research part 2: designing a survey , 2002, SOEN.

[38]  Adam A. Porter,et al.  Empirical studies of software engineering: a roadmap , 2000, ICSE '00.

[39]  Philippe Kruchten,et al.  Wishes and Boundaries for a Software Architecture Knowledge Community , 2008, Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008).