The Decision View of Software Architecture

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.

[1]  Douglas Stuart,et al.  Dependency Navigation in Product Lines Using XML , 2000, IW-SAPF.

[2]  Philippe Krutchen,et al.  Architectural blueprints--the '4+1' view model of software architecture , 1995 .

[3]  Alexander L. Wolf,et al.  Software architecture , 2001 .

[4]  Juan Antonio de la Puente,et al.  Framework for documenting design decisions in product families development , 1997, Proceedings. Third IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.97TB100168).

[5]  G. Turnbull.  Industrial Experience Report , 1999, EUROMICRO.

[6]  Alexander L. Wolf,et al.  Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .

[7]  Gonzalo León,et al.  An introduction to evolution of large systems based on Software Architecture , 1998, Systems Implementation 2000.

[8]  David Garlan,et al.  Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..

[9]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[10]  Mehdi Jazayeri,et al.  Software Architecture for Product Families: Principles and Practice , 2000 .

[11]  Michael Eonsuk Shin,et al.  A Multiple-View Meta-modeling Approach for Variability Management in Software Product Lines , 2004, ICSR.

[12]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[13]  Flavio Oquendo,et al.  Software Architecture , 2004, Lecture Notes in Computer Science.

[14]  Jan Bosch,et al.  Software Reuse: Methods, Techniques, and Tools , 2004, Lecture Notes in Computer Science.

[15]  Eoin Woods,et al.  Experiences Using Viewpoints for Information Systems Architecture: An Industrial Experience Report , 2004, EWSA.

[16]  Frank van der Linden,et al.  Software Architectures for Product Families , 2000, Lecture Notes in Computer Science.

[17]  J. C. Dueñas.  HYPER-LINKED SOFTWARE ARCHITECTURES FOR CONCURRENT ENGINEERING , 2002 .

[18]  Shmuel Katz,et al.  Architectural views of aspects , 2003, AOSD '03.

[19]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

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

[21]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[22]  Bas Graaf.  Maintainability through Architecture Development , 2004, EWSA.