Visualizing Software Architectural Design Decisions

  • Larix Lee
  • Philippe Kruchten
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5292)


Software architecture can be represented as a set of design decisions. Exploring and analyzing architectural design decisions are difficult due to how the decisions are represented and displayed. We describe four visualization aspects that apply to architectural design decision exploration and analysis: 1) tabular listing; 2) decision structure visualization; 3) decision chronology visualization; and 4) decision impact visualization. These aspects address some situations where visualization helps people understand and utilize decisions.


Design Decision Decision Structure Decision Attribute Decision Information Node Circle 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Bosch, J.: Software Architecture: The Next Step. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds.) EWSA 2004. LNCS, vol. 3047, pp. 194–199. Springer, Heidelberg (2004)Google Scholar
  2. 2.
    Duenas, J.C., Capilla, R.: The Decision View of Software Architecture. In: Morrison, R., Oquendo, F. (eds.) EWSA 2005. LNCS, vol. 3527, pp. 222–230. Springer, Heidelberg (2005)Google Scholar
  3. 3.
    Jansen, A., Bosch, J.: Software Architecture as a Set of Architectural Design Decisions. In: Proc. 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 2005), pp. 109–120. IEEE Computer Society, Pittsburgh (2005)CrossRefGoogle Scholar
  4. 4.
    Kruchten, P.: An Ontology of Architectural Design Decisions. In: Bosch, J. (ed.) Proc. 2nd Groningen Workshop on Software Variability Management, pp. 55–62. Rijksuniversiteit Groningen, Groningen (2004)Google Scholar
  5. 5.
    Kunz, W., Rittel, H.W.J.: Issues as Elements of Information Systems, Working Paper 131. Institute of Urban and Regional Development. The University of California at Berkeley, Berkeley (1970)Google Scholar
  6. 6.
    Lee, L., Kruchten, P.: Customizing the Capture of Software Architectural Design Decisions. In: Proc. 21st Canadian Conference on Electrical and Computer Engineering, pp. 693–698. IEEE, Niagara Falls (2008)CrossRefGoogle Scholar
  7. 7.
    Lee, L., Kruchten, P.: A Tool to Visualize Architectural Design Decisions. In: Becker, S., Plasil, F. (eds.) QoSA 2008. LNCS, vol. 5281, pp. 43–54. Springer, Heidelberg (2008)Google Scholar
  8. 8.
    Tyree, J., Ackerman, A.: Architecture Decisions: Demystifying Architecture. IEEE Software 22(2), 19–27 (2005)CrossRefGoogle Scholar
  9. 9.
    van der Ven, J.S., Jansen, A.G.J., Avgeriou, P., Hammer, D.K.: Using Architectural Decisions. In: Hofmeister, C., Crnković, I., Reussner, R. (eds.) QoSA 2006. LNCS, vol. 4214, pp. 1–10. Springer, Heidelberg (2006)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Larix Lee
    • 1
  • Philippe Kruchten
    • 1
  1. 1.University of British Columbia 

Personalised recommendations