This Article 
 Bibliographic References 
 Add to: 
Making Practical Use of Quality Attribute Information
March/April 2008 (vol. 25 no. 2)
pp. 25-33
Quality attribute requirements are important both for customer and end-user satisfaction and for driving software system design. Yet asserting their importance raises many other questions. In particular, using quality attribute information in practice isn't obvious. Here, we consider two aspects of using such information: communicating with stakeholders about quality attributes and incorporating quality attribute requirements into existing analysis and design methods.

1. IS0 9126-1 Information Technology—Software Product Evaluation—Quality Characteristics and Guidelines for Their Use, Int'l Organization for Standardization, 2001.
2. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, 2nd ed., Addison-Wesley, 2003.
3. C. Larman, Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd ed., Prentice Hall, 2004.
4. K. Wiegers, Software Requirements, 2nd ed., Microsoft Press, 2003.
5. D. Budgen, Software Design, Addison-Wesley, 2003.
6. N. Mullick et al., "Siemens Global Studio Project: Experiences Adopting an Integrated GSD Infrastructure," Proc. IEEE Int'l Conf. Global Software Eng. (ICGSE06), IEEE Press, 2006, pp. 203–212.
7. 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.
8. J. Cheesman and J. Daniels, UML Components: A Simple Process for Specifying Component-Based Software, Addison-Wesley, 2001.
9. P. Kroll and P. Kruchten, The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP, Addison-Wesley, 2003.
10. P. Eeles, "Capturing Architectural Requirements," IBM DeveloperWorks,15 Nov. 2005, library4706.html.
11. H. Eriksson and M. Penker, Business Modeling with UML: Business Patterns at Work, OMG Press, 2000.
12. R. Kazman et al., Integrating Software Architecture-Centric Methods into the Rational Unified Process, tech. report CMU/SEI-2004-TR-011, SEI, Carnegie Mellon Univ., 2004.
13. R.L. Nord and J.E. Tomayko, "Software Architecture-Centric Methods and Agile Development," IEEE Software, vol. 23, no. 2, 2006, pp. 47–53.
14. R.L. Nord et al., Proc. 1st Software Architecture Technology User Network (SATURN) Workshop, tech. note CMU/SEI-2005-TN-037, SEI, Carnegie Mellon Univ., 2005.
15. Proc. 3rd SEI Software Architecture Technology User Network Workshop (SATURN07), SEI, Carnegie Mellon Univ., 2007, tech_program.html.

Index Terms:
Design methodology,Software systems,Taxonomy,Software engineering,Software design,ISO standards,Automatic control,Control systems,Information analysis,Terminology,architecture-centric design methods,quality attribute requirements,software system design,quality attribute scenarios,utility tree,attribute driven design,object oriented analysis and design
"Making Practical Use of Quality Attribute Information," IEEE Software, vol. 25, no. 2, pp. 25-33, March-April 2008, doi:10.1109/MS.2008.39
Usage of this product signifies your acceptance of the Terms of Use.