This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
March/April 2008 (vol. 25 no. 2)
pp. 22-24
J. David Blaine, independent consultant
Jane Cleland-Huang, DePaul University
The elicitation, analysis, and specification of quality requirements involve careful balancing of a broad spectrum of competing priorities. Developers must therefore focus on identifying qualities and designing solutions that optimize the product's value to its stakeholders.

1. K.E. Wiegers, Software Requirements, 2nd ed., Microsoft Press, 2003.
2. T. Gilb, Principles of Software Engineering Management, Addison-Wesley, 1988.
3. T. Gilb, Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage, Butterworth-Heinemann, 2005.
4. L. Chung et al., Nonfunctional Requirements in Software Engineering, Kluwer Academic Publishers, 2000.
5. B.W. Boehm et al., "Using the WinWin Spiral Model: A Case Study," Computer, vol. 31, no. 7, 1998, pp. 33–44.

Index Terms:
Quality requirements, non-functional requirements, product value, architectural qualities
Citation:
J. David Blaine, Jane Cleland-Huang, "Software Quality Requirements: How to Balance Competing Priorities," IEEE Software, vol. 25, no. 2, pp. 22-24, March-April 2008, doi:10.1109/MS.2008.46
Usage of this product signifies your acceptance of the Terms of Use.