Towards Decision Centric Repository of Architectural Knowledge

  • Bartosz Michalik
  • Jerzy Nawrocki
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7054)


Architectural design and design decisions are the key components of architectural knowledge. However, concerns, rationales, and risks should be also captured to prevent knowledge vaporization. So, how to deal with architectural knowledge in incremental knowledge refinement? We believe that usage of the knowledge repository system can support architecture evolution. In this paper, a model of knowledge repository is presented. In this model, the decision-centric approach is complemented with the architectural views to support indirect interrelations between design decisions. Support for agile development was one of the key aspects of the model design, therefore knowledge vaporisation might be reduced.


Architectural knowledge management Architectural design decisionsPart I Architectural description 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Clements, D.: Documenting Software Architectures: Views and Beyond. Addison-Wesley Professional (2002)Google Scholar
  2. 2.
    Kruchten, P., Lago, P., van Vliet, H.: Building Up and Reasoning About Architectural Knowledge. In: Hofmeister, C., Crnković, I., Reussner, R. (eds.) QoSA 2006. LNCS, vol. 4214, pp. 43–58. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  3. 3.
    Kruchten, P.: The 4+ 1 View Model of architecture. IEEE Software 12(6), 42–50 (1995)CrossRefGoogle Scholar
  4. 4.
    Kennaley, M.: The 3+1 Views of Architecture (in 3d): An Amplification of the 4+1 Viewpoint Framework. In: Proc. of the 7th Working IEEE/IFIP Conference on Software Architecture (WICSA 2008), pp. 299–302. IEEE Computer Society (2008)Google Scholar
  5. 5.
    IEEE 1471:2000–Recommended Practice for Architectural Description of Software Intensive Systems (2000)Google Scholar
  6. 6.
    ISO/IEC: ISO/IEC 42010 (IEEE P42010), Systems and Software Engineering – Architecture Description, WD3 (2008)Google Scholar
  7. 7.
    Jansen, A., Bosch, J.: Software Architecture as a Set of Architectural Design Decisions. In: Proc. of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 2005), pp. 109–120. IEEE Computer Society (2005)Google Scholar
  8. 8.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley Professional (2003)Google Scholar
  9. 9.
    Hofmeister, C., Nord, R., Soni, D.: Applied Software Architecture. Addison-Wesley Professional (1999)Google Scholar
  10. 10.
    Tang, A., Jin, Y., Han, J.: A Rationale-based Architecture Model for Design Traceability and Reasoning. Journal of Systems and Software 80(6), 918–934 (2007)CrossRefGoogle Scholar
  11. 11.
    Wang, Z., Sherdil, K., Madhavji, N.H.: Acca: An Architecture-centric Concern Analysis Method. In: Proc. of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 2005), pp. 99–108. IEEE Computer Society (2005)Google Scholar
  12. 12.
    Jansen, A., Bosch, J.: Evaluation of Tool Support for Architectural Evolution. In: Proc. of the 19th IEEE International Conference on Automated Software Engineering (ASE 2004), pp. 375–378. IEEE (2004)Google Scholar
  13. 13.
    Babar, M., Gorton, I.: A Tool for Managing Software Architecture Knowledge. In: Proc. of the 2nd Workshop on Sharing and Reusing Architectural Knowledge, Rationale, and Design Intent, p. 11. IEEE (2007)Google Scholar
  14. 14.
    Capilla, R., Nava, F., Pérez, S., Dueñas, J.: A Web-based Tool for Managing Architectural Design Decisions. ACM SIGSOFT Software Engineering Notes 31(5) (2006)Google Scholar
  15. 15.
    Jansen, A., Van der Ven, J., Avgeriou, P., Hammer, D.: Tool Support for Architectural Decisions. In: Proc. of the 6th Working IEEE/IFIP Conference on Software Architecture (WICSA 2007), p. 4. IEEE Computer Society (2007)Google Scholar
  16. 16.
    Kruchten, P., Lago, P., van Vliet, H., Wolf, T.: Building up and Exploiting Architectural Knowledge. In: Proc. of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 2005), pp. 291–292. IEEE Computer Society (2005)Google Scholar
  17. 17.
    Tyree, J., Akerman, A.: Architecture Decisions: Demystifying Architecture. IEEE Software 22(2), 19–27 (2005)CrossRefGoogle Scholar
  18. 18.
    Kleppe, A., Warmer, J., Bast, W.: MDA Explained: The Model Driven Architecture–Practice and Promise. Addison-Wesley Professional (2003)Google Scholar
  19. 19.
    Kruchten, P.: An Ontology of Architectural Design Decisions in Software Intensive Systems. In: Proc. of the 2nd Groningen Workshop on Software Variability, pp. 54–61 (2004)Google Scholar
  20. 20.
    Software Engineering – Software Product Quality Requirements and Evaluation (SQuaRE) – Guide to SQuaRE. ISO/IEC 25000:2005(E) (2005)Google Scholar
  21. 21.
    Michalik, B., Nawrocki, J., Ochodek, M.: 3-step Knowledge Transition: a Case Study on Architecture Evaluation. In: Proc. of the 30th International Conference on Software Engineering, pp. 741–748. ACM, New York (2008)Google Scholar
  22. 22.
    Clements, P., Kazman, R., Klein, M.: Evaluating Software Architectures. Addison-Wesley, Boston (2002)Google Scholar
  23. 23.
    Garlan, D., Monroe, R., Wile, D.: Acme: An Architecture Description Interchange Language. In: Proc. of the 1997 Conference of the Centre for Advanced Studies on Collaborative Research, pp. 169–183. IBM Press (1997)Google Scholar
  24. 24.
    Herzberg, D.: UML-RT as a Candidate for Modeling Embedded Real-Time Systems in the Telecommunication Domain. In: France, R.B. (ed.) UML 1999. LNCS, vol. 1723, pp. 330–338. Springer, Heidelberg (1999)CrossRefGoogle Scholar
  25. 25.
    Bjerkander, M., Kobryn, C.: Architecting Systems with UML 2.0. IEEE Software 20(4), 57–61 (2003)CrossRefGoogle Scholar
  26. 26.
    Alliance, O.: Osgi Service Platform, Core Specification Release 4. Draft (July 2005)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2012

Authors and Affiliations

  • Bartosz Michalik
    • 1
  • Jerzy Nawrocki
    • 1
  1. 1.Institute of Computing SciencePoznan University of TechnologyPoznańPoland

Personalised recommendations