The Decision View of Software Architecture

  • Juan C. Dueñas
  • Rafael Capilla
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3527)


Documenting software architectures is a key aspect to achieve success when communicating the architecture to different stakeholders. Several architectural views have been used with different purposes during the design process. The traditional view on software architecture defines this in terms of components and connectors. Also, the “4+1” view model proposes several views from the same design to satisfy the interests of the different stakeholders involved in the modelling process. In this position paper we try to go a step beyond previous proposals, to detail the idea of considering the architecture as a composition of architectural design decisions. We will propose a set of elements, information and graphical notation to record the design decisions during the modelling process.


Design Decision Software Architecture Product Family Quality Function Deployment Software Product Line 
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.
    Alonso, A., León, G., Dueñas, J.C., de la Puente, J.A.: Framework for documenting design decisions in product families development. In: Proceedings of the Third International Conference on Engineering of Complex Computer Systems, Como, Italia (September 1997)Google Scholar
  2. 2.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. Addison-Wesley, Reading (2003)Google Scholar
  3. 3.
    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)CrossRefGoogle Scholar
  4. 4.
    Chung, L., Nixon, B., Yu, E., Mylopoulos, J.: Non-functional requirements in software engineering. Kluwer Academic Publishers, Dordrecht (2000)zbMATHGoogle Scholar
  5. 5.
    Clements, P., Bachman, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., Stafford, J.: Documenting Software Architectures. In: Views and Beyond. Addison-Wesley, Reading (2003)Google Scholar
  6. 6.
    Dueñas, J.C., Hauswirth, M.: Hyper-linked Software Architectures for Concurrent Engineering. In: Proceedings of Concurrent Engineering Europe 1997, Erlangen-Nuremberg, Germany, pp. 3–10. Society for Computer Simulation (1997)Google Scholar
  7. 7.
    Dueñas, J.C., León, G.: An introduction to evolution of large systems based on Software Architectures. In: Systems Implementation 2000, IFIP TC2 WG2.4 Working Conference on Systems Implementation 2000, Berlin, Germay, pp. 128–139. Chapman and Hall, Boca Raton (1998)Google Scholar
  8. 8.
    Gomaa, H., Shin, E.: A Multiple View Meta-modeling Approach for Variability Management in Software Product Lines. In: Bosch, J., Krueger, C. (eds.) ICOIN 2004 and ICSR 2004. LNCS, vol. 3107, pp. 274–285. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  9. 9.
    Graaf, L.: Maintainability through Architecture Development. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds.) EWSA 2004. LNCS, vol. 3047, pp. 206–211. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  10. 10.
    IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE Std 1471-2000 (2000) Google Scholar
  11. 11.
    Jazayeri, M., Ran, A., van der Linden (eds.): Software Architecture for Product Families. Addison-Wesley, Reading (2000)Google Scholar
  12. 12.
    Katara, M., Katz, S.: Architectural Views of Aspects. In: Proceedings of AOSD 2003, Boston, USA, pp. 1–10. ACM, New York (2003)CrossRefGoogle Scholar
  13. 13.
    Kruchten, P.: Architectural Blueprints. The “4+1” View Model of Software Architecture. IEEE Software 12(6), 42–50 (1995)CrossRefGoogle Scholar
  14. 14.
    Perry, D., Wolf, A.: Foundations for the Study of Software Architecture. ACM SIGSOFT Software Engineering Notes 17(4) (October 1992)Google Scholar
  15. 15.
    Shaw, M., Garlan, D.: Software Architecture. Prentice-Hall, Englewood Cliffs (1996)Google Scholar
  16. 16.
    Stuart, D., Sull, W., Cook, T.W.: Dependency Navigation in Product Lines Using XML. In: van der Linden, F.J. (ed.) IW-SAPF 2000. LNCS, vol. 1951, p. 82. Springer, Heidelberg (2000)CrossRefGoogle Scholar
  17. 17.
    Woods, E.: Experiences Using Viewpoints for Information Systems Architecture: An Industrial Experience Report. In: Oquendo, F., Warboys, B.C., Morrison, R. (eds.) EWSA 2004. LNCS, vol. 3047, pp. 182–193. Springer, Heidelberg (2004)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Juan C. Dueñas
    • 1
  • Rafael Capilla
    • 2
  1. 1.Department of Engineering of Telematic Systems, ETSI TelecomunicaciónUniversidad Politécnica de MadridMadridSpain
  2. 2.Department of Informatics and TelematicsUniversidad Rey Juan CarlosMadridSpain

Personalised recommendations