This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Decision View's Role in Software Architecture Practice
March/April 2009 (vol. 26 no. 2)
pp. 36-42
ASCII Text
x 
 
Philippe Kruchten, Rafael Capilla, Juan Carlos Dueñas, "The Decision View's Role in Software Architecture Practice," IEEE Software, vol. 26, no. 2, pp. 36-42, March/April, 2009.
 
 
BibTex
x
 
@article{ 10.1109/MS.2009.52,
author = {Philippe Kruchten and Rafael Capilla and Juan Carlos Dueñas},
title = {The Decision View's Role in Software Architecture Practice},
journal ={IEEE Software},
volume = {26},
number = {2},
issn = {0740-7459},
year = {2009},
pages = {36-42},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.52},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - The Decision View's Role in Software Architecture Practice
IS - 2
SN - 0740-7459
SP36
EP42
EPD - 36-42
A1 - Philippe Kruchten,
A1 - Rafael Capilla,
A1 - Juan Carlos Dueñas,
PY - 2009
KW - software architecture
KW - architectural design decision
KW - architectural knowledge
KW - architecture views
KW - decision view
VL - 26
JA - IEEE Software
ER -
 
Philippe Kruchten, University of British Columbia
Rafael Capilla, Universidad Rey Juan Carlos
Juan Carlos Dueñas, Universidad Politécnica de Madrid
A decision view provides a useful complement to the traditional sets of architectural views and viewpoints. It gives an explanatory perspective that illuminates the reasoning process itself and not solely its results. The decision view documents aspects of the architecture that are hard to reverse-engineer from the software itself and that are often left tacit. The decision view and the decisions that it captures embody high-level architectural knowledge that can be transferred to other practitioners and merged when systems are merged, and they offer useful support for maintaining large, long-lived software-intensive systems. This article leads readers through a succession of epiphanies: from design to architecture, then architecture representation to architecture design methods, and finally to architectural design decisions.

1. W.W. Gibbs, "Software's Chronic Crisis," Scientific American, vol. 271, Sept. 1994, pp. 72–81.
2. P. Kruchten, H. Obbink, and J. Stafford, "The Past, Present, and Future of Software Architecture," IEEE Software, vol. 23, no. 2, 2006, pp. 22–30.
3. D.E. Perry and A.L. Wolf, "Foundations for the Study of Software Architecture," ACM Software Eng. Notes, vol. 17, no. 4, 1992, pp. 40–52.
4. P.. Kruchten, The Rational Unified Process—An Introduction, 3rd ed., Addison-Wesley, 2003.
5. IEEE Std. 1471-2000, Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE, 2000.
6. P. Kruchten, "The 4+1 View Model of Architecture," IEEE Software, vol. 12, no. 6, 1995, pp. 45–50.
7. C. Hofmeister, R. Nord, and D. Soni, Applied Software Architecture, Addison-Wesley, 1999.
8. C. Hofmeister et al., "A General Model of Software Architecture Design Derived from Five Industrial Approaches," J. Systems and Software, vol. 80, no. 1, 2007, pp. 106–126.
9. P. Clements et al., Documenting Software Architectures: Views and Beyond, Addison-Wesley, 2002.
10. N. Rozanski and E. Woods, Software Systems Architecture, Addison-Wesley, 2005.
11. I. Rus and M. Lindvall, "Knowledge Management in Software Engineering," IEEE Software, vol. 19, no. 3, 2002, pp. 26–38.
12. J. Bosch, "Software Architecture: The Next Step," Proc. 1st European Workshop Software Architecture (EWSA 04), LNCS 3047, Springer, 2004, pp. 194–199.
13. P. Kruchten, P. Lago, and H. van Vliet, "Building Up and Reasoning about Architectural Knowledge," Proc. 2nd Int'l Conf. Quality of Software Architectures (QoSA 06), LNCS 4214, Springer, 2006, pp. 43–58.
14. J. Tyree and A. Akerman, "Architecture Decisions: Demystifying Architecture," IEEE Software, vol. 22, no. 2, 2005, pp. 19–27.
15. R. Capilla, F. Nava, and J.C. Dueñas, "Modeling and Documenting the Evolution of Architectural Design Decisions," Proc. 2nd Workshop Sharing and Reusing Architectural Knowledge Architecture, Rationale, and Design Intent, IEEE CS Press, 2007, p. 9.
16. T. Käkölä and J.C. Dueñas eds., Software Product Lines—, Research Issues in Engineering and Management, Springer, 2006.
17. A.H. Dutoit et al., eds., Rationale Management in Software Engineering, Springer, 2006.
18. P. Lago and P. Avgeriou, "First ACM Workshop on Sharing and Reusing Architectural Knowledge (Shark)," ACM SIGSOFT Software Eng. Notes, vol. 31, no. 5, 2006, pp 32–36.
19. D. Falessi, R. Capilla, and G. Cantone, "A Value-Based Approach for Documenting Design Decisions Rationale: A Replicated Experiment," Proc. 3rd Int'l Workshop Sharing and Reusing Architectural Knowledge (Shark 08), ACM Press, 2008, pp. 63–70.
20. R. Capilla, F. Nava, and R. Carrillo, "Effort Estimation in Capturing Architectural Knowledge," Proc. 23rd IEEE/ACM Int'l Conf. Automated Software Eng., IEEE Press, 2008, pp. 208–217.
21. J.C. Dueñas and R. Capilla, "The Decision View of Software Architecture," Proc. 2nd European Workshop Software Architecture (EWSA 05), LNCS 3047, Springer, 2005, pp. 222–230.

Index Terms:
software architecture, architectural design decision, architectural knowledge, architecture views, decision view
Citation:
Philippe Kruchten, Rafael Capilla, Juan Carlos Dueñas, "The Decision View's Role in Software Architecture Practice," IEEE Software, vol. 26, no. 2, pp. 36-42, March-April 2009, doi:10.1109/MS.2009.52
Usage of this product signifies your acceptance of the Terms of Use.