The Community for Technology Leaders
RSS Icon
Issue No.06 - November/December (2010 vol.27)
pp: 33-37
Juha Savolainen , Nokia Research Center, Finland
Tomi Männistö , Aalto University
Much work on software architectures has focused on how to document them. This has improved the understanding of real-life architectures. However, when multiple stakeholder concerns need to be addressed, they easily become scattered throughout the documentation. One reason might be that architectural views typically don't support the easy evaluation of trade-offs between conflicting quality attributes. When these concerns and related architectural decisions are distributed among many views, they are less obvious to architects and stakeholders. The authors propose an approach to creating architectural views that more prominently communicate the conflicts between key stakeholders' concerns. The approach also tends to reduce the amount of architectural documentation and thus increase its communication value by highlighting architectural decisions made to resolve the conflicts identified.
software architecture, software engineering
Juha Savolainen, Tomi Männistö, "Conflict-Centric Software Architectural Views: Exposing Trade-Offs in Quality Requirements", IEEE Software, vol.27, no. 6, pp. 33-37, November/December 2010, doi:10.1109/MS.2010.139
1. D. Soni, R.L. Nord, and C. Hofmeister, "Software Architecture in Industrial Applications," Proc. 17th Int'l Conf. Software Eng. (ICSE 95), ACM Press, 1995, pp. 196–207.
2. N. Lassing, N. Rijsenbrij, and H. van Vliet, "Viewpoints on Modifiability," Int'l J. Software Eng. and Knowledge Eng., vol 11, no. 4, 2001, pp. 453–478.
3. A. Ran and J. Kuusela, "Design Decision Trees," Proc. 8th Int'l Workshop Software Specification and Design (IWSSD 96), IEEE CS Press, 1996, p. 172.
4. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison-Wesley, 2003.
5. B. Boehm and H. In, "Identifying Quality-Requirement Conflicts," IEEE Software, vol. 13, no. 2, 1996, pp. 25–35.
6. N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives, Addison-Wesley, 2005.
7. ISO/IEC Std. 42010-2007(E), Systems and Software Engineering — Recommended Practice for Architectural Description of Software-Intensive Systems, ISO/IEC, 2007.
8. P.B. Kruchten, "The 4 + 1 View Model of Architecture," IEEE Software, vol. 12, no. 6, 1995, pp. 42–50.
9. J.A. Zachman, "A Framework for Information Systems Architecture," IBM Systems J., vol. 26, no. 3, 1987, pp. 276–292.
24 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool