The Decision View of Software Architecture Export

@incollection{citeulike:3687112, abstract = {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.}, author = {Due\~{n}as, Juan C. and Capilla, Rafael}, citeulike-article-id = {3687112}, citeulike-linkout-0 = {http://dx.doi.org/10.1007/11494713_15}, citeulike-linkout-1 = {http://www.springerlink.com/content/g0xcuw2ureayvlpp}, doi = {10.1007/11494713_15}, journal = {Software Architecture}, keywords = {decisions, documentation, software, software-architecture, software-engineering}, pages = {222--230}, posted-at = {2009-05-26 15:04:15}, priority = {0}, title = {The Decision View of Software Architecture}, url = {http://dx.doi.org/10.1007/11494713_15}, year = {2005} }

TY - CHAP ID - citeulike:3687112 L3 - citeulike-article-id:3687112 N2 - 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. JF - Software Architecture EP - 230 TI - The Decision View of Software Architecture SP - 222 KW - decisions KW - documentation KW - software KW - software-architecture KW - software-engineering AU - Dueñas, Juan AU - Capilla, Rafael PY - 2005/// UR - http://dx.doi.org/10.1007/11494713_15 ER -