This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Value-Focused System Quality
November/December 2010 (vol. 27 no. 6)
pp. 84-86
ASCII Text
x 
 
Frank Buschmann, "Value-Focused System Quality," IEEE Software, vol. 27, no. 6, pp. 84-86, November/December, 2010.
 
 
BibTex
x
 
@article{ 10.1109/MS.2010.150,
author = {Frank Buschmann},
title = {Value-Focused System Quality},
journal ={IEEE Software},
volume = {27},
number = {6},
issn = {0740-7459},
year = {2010},
pages = {84-86},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2010.150},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Value-Focused System Quality
IS - 6
SN - 0740-7459
SP84
EP86
EPD - 84-86
A1 - Frank Buschmann,
PY - 2010
KW - nonfunctional quality
KW - architecture quality
KW - value-based design
VL - 27
JA - IEEE Software
ER -
 
Frank Buschmann, Siemens Corporate Technology
Experts never tire of emphasizing that software architectures should support appropriate system qualities to be useful and sustainable. Experience, in contrast, shows that the architectures of many software systems are casually, even haphazardly, structured, making it hard to sufficiently support any system quality. The author thus advocates a design style that takes the value that nonfunctional qualities contribute to a system's business success as the ultimate measure to decide what operational and developmental qualities a system really needs, where in a system the qualities are needed, and how "good" these qualities must be.

1. B. Foote and J.W. Yoder, "Big Ball of Mud," Pattern Languages of Program Design 4, N. Harrison, B. Foote, and H. Rohnert eds., Addison-Wesley, 2000, pp. 653–692.
2. F. Buschmann, "Does Architecture Quality Matter?,", panel at Java and Object-Oriented Conf. (JAOO '07), 2007; http://jaoo.dk/aarhus2007/speakerTrack+host%3A+Frank+Buschmann.
3. F. Buschmann, "Learning from Failure, Part I: Scoping and Requirements Woes," IEEE Software, vol. 26, no. 6, 2009, pp. 68–69.
4. W. Adams, "Letters," IEEE Software, vol. 27, no. 1, 2010, pp. 7–8.
5. F. Buschmann, "Learning from Failure, Part II: Featuritis, Performitis, and Other Diseases," IEEE Software, vol. 27, no. 1, 2010, pp. 10–11.
6. F. Buschmann, "Learning from Failure, Part III: On Hammers and Nails, and Falling in Love with Technology and Design," IEEE Software, vol. 27, no. 2, 2010, pp. 49–51.
7. F. Buschmann and K. Henney, "Five Considerations for Software Architecture, Part 1," IEEE Software, vol. 27, no. 3, 2010, pp. 63–65.
8. F. Buschmann and K. Henney, "Five Considerations for Software Architecture, Part 2," IEEE Software, vol. 27, no. 4, 2010, pp. 12–14.

Index Terms:
nonfunctional quality, architecture quality, value-based design
Citation:
Frank Buschmann, "Value-Focused System Quality," IEEE Software, vol. 27, no. 6, pp. 84-86, Nov.-Dec. 2010, doi:10.1109/MS.2010.150
Usage of this product signifies your acceptance of the Terms of Use.