Institute for

Architectural Knowledge Hubs

Online Resources for Software Architects

Updates available on new personal blog "The Concerned Architect", example: "Awesome Architecture Descriptions and Pattern Languages".


The November/December 2016 Theme Issue of IEEE Software on the Role of the Software Architect in the Digital Age is a good starting point - for instance, the Guest Editor's Introduction to the Theme Issue (PDF).

 Websites by thought leaders that we frequently consult (among many others):

  1. Martin Fowler's Bliki
  2. Gregor Hohpe's Ramblings
  3. Philippe Kruchten's Weblog
  4. Eoin Wood's website
  5. Michael Stal's software architecture blog
  6. The Software Architecture Handbook website by Grady Booch
  7. Personal page of Gernot Starke (mostly in German) - arc42, aim42, IT architect profession
  8. Technical Reports and other publications in the Digital Library of the Software Engineering Institute (SEI)
  9. The Open Group website - IT Architect Certification, TOGAF, ArchiMate, XA
  10. Agile Alliance, e.g. Agile 101
  11. Object Management Group (OMG) - UML, SPEM, MDA, CORBA, ADM, KDM
  12. IEEE Software, as well as SWEBOK and the very readable standard for architecture descriptions, ISO/IEC/IEEE 42010


Academic conferences (software architecture research): ICSA, ECSA and online archives: ACM Digital Library, IEEE Xplore and ScienceDirect.


The following conferences have a practitioner focus on all things software architecture are (most of the presentations are available online and can be accessed from the conference websites):

  1. SEI SATURN, e.g. SATURN 2013
  2. Industry Day at CompArch/WICSA 2011
  3. ECSA 2014 also had an Industry Day
  4. OOP (most talks in German, presentations not available online by default)
  5. SPLASH and OOPSLA (e.g. practitioners reports program at OOPSLA 2008)


If you are new to the field, you can get started by reviewing the arc42 site (in German). If you have a little more time to study, many excellent books on the topic are available to you, including (but of course not limited to):

  1. Software Systems Architecture (Second Edition) by Nick Rozanski and Eoin Woods introduces core architecture concepts, as well as a viewpoint- and perspective-based architecture framework.
  2. Just Enough Software Architecture by George Fairbanks proposes a pragmatic and risk-driven approach to design method tailoring and modeling. Design It! by Michael Keeling make software architecture lightweight and flexible (to avoid the term agile here) and presented a rich toolbox that comes with highly educational examples. 
  3. The Process of Software Architecting by Peter Cripps and Peter Eeles is a comprehensive reference for architecting tasks, work products (a.k.a. artifacts) and abstraction-realization levels.
  4. Design It! by Michael Keeling (2017). This book in the Pragmatic Programmers series by Michael Keeling make software architecture lightweight and flexible (to avoid the term agile here) and presented a rich toolbox that comes with highly educational examples.
  5. (in German), Effektive Softwarearchitekturen by Gernot Starke
  6. Continuous Software Architecture in Practice by Murat Erder, Pierre Pureur and Eoin Woods is a 2021 newcomer to this list.
  7. Design Practice Reference by Olaf Zimmermann and Mirko Stocker continues to collect and curate knowledge from these and other sources.


If you think that you do not need any architecture design because you apply agile practices and the architecture of the system under construction will emerge silently during refactoring, please read through some of the following references:

  1. Ken Schwaber's original Scrum paper from OOPSLA '97 (hint: have a look at pages 10, 12, and 13).
  2. ThoughtWorks presentation Agilists and Architects: Allies not Adversaries (Rebecca Parsons, Martin Fowler).
  3. Philippe Kruchten's blog post on Agile Architecture.
  4. IEEE Software, Special Issue on Agility and Architecture (March/April 2010).
  5. The Agile Architecting Library at the Software Engineering Institute (SEI).

Bottom line: run a an architectural spike (or Sprint Zero or Pregame including High-Level Design work) and maintain a decision backlog in addition to a product backlog!


Contact for this page: Olaf Zimmermann