This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
A Risk-Based, Value-Oriented Approach to Quality Requirements
March/April 2008 (vol. 25 no. 2)
pp. 34-41
Martin Glinz, University of Zurich
Quality requirements, i.e. those requirements that pertain to a system's quality attributes, are traditionally regarded to be useful only when they are represented quantitatively so that they can be measured. This article presents a value-oriented approach to specifying quality requirements that deviates from the classic approach. This approach uses a broad range of potential representations that are selected on the basis of risk assessment. Requirements engineers select a quality requirement representation such that they get an optimal balance between mitigating the risk of developing a system that doesn't satisfy the stakeholders' desires and needs on the one hand and the cost of specifying the requirement in the selected representation on the other hand. This issue is part of a special issue on quality requirements.

1. B. Boehm, J.R. Brown, and M. Lipow, "Quantitative Evaluation of Software Quality," Proc. 2nd Int'l Conf. Software Eng., ACM Press, 1976, pp. 592–605.
2. T. Gilb, Principles of Software Engineering Management, Addison-Wesley, 1988.
3. ISO/IEC 9126-1: Software Engineering—Product Quality—Part 1: Quality Model, Int'l Organization for Standardization, 2001.
4. ISO/IEC 25030: Software Engineering—Software Product Quality Requirements and Evaluation (SQUARE)—Quality Requirements, Int'l Organization for Standardization, 2007.
5. N.E. Fenton and S.L. Pfleeger, Software Metrics: A Rigorous and Practical Approach, 2nd ed., PWS Publishing, 1998.
6. M. Glinz and R. Wieringa, "Stakeholders in Requirements Engineering," guest editors' introduction, IEEE Software, vol. 24, no. 2, 2007, pp. 18–20.
7. A. Davis, Just Enough Requirements Management, Dorset House, 2005.
1. M. Glinz, "On Non-Functional Requirements," Proc. 15th IEEE Int'l Requirements Eng. Conf. (RE'07), IEEE CS Press, pp. 21–26.
2. ISO/IEC 25030: Software Engineering—Software Product Quality Requirements and Evaluation (SQUARE)—Quality Requirements, Int'l Organization for Standardization, 2007.
1. N.E. Fenton and S.L. Pfleeger, Software Metrics: A Rigorous and Practical Approach, 2nd ed., PWS Publishing, 1998.
2. ISO/IEC 25020: Software Engineering—Software Product Quality Requirements and Evaluation (SQUARE)—Measurement Reference Model and Guide, Int'l Organization for Standardization, 2007.
3. T. Gilb, Principles of Software Engineering Management, Addison-Wesley, 1988.
4. T. Gilb, Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage, Butterworth-Heinemann, 2005.
1. ISO/IEC 9126-1: Software Engineering—Product Quality—Part 1: Quality Model, Int'l Organization for Standardization, 2001.
2. ISO/IEC TR 9126-2: Software Engineering—Product Quality—Part 2: External Metrics, Int'l Organization for Standardization, 2003.
3. ISO/IEC TR 9126-3: Software Engineering—Product Quality—Part 3: Internal Metrics, Int'l Organization for Standardization, 2003.
4. ISO/IEC TR 9126-4: Software Engineering—Product Quality—Part 4: Quality in Use Metrics, Int'l Organization for Standardization, 2004.
5. ISO/IEC 25020: Software Engineering—Software Product Quality Requirements and Evaluation (SQUARE)—Measurement Reference Model and Guide, Int'l Organization for Standardization, 2007.
6. ISO/IEC 25030: Software Engineering—Software Product Quality Requirements and Evaluation (SQUARE)—Quality Requirements, Int'l Organization for Standardization, 2007.

Index Terms:
Quality requirements, Quantification, Risk, Value
Citation:
Martin Glinz, "A Risk-Based, Value-Oriented Approach to Quality Requirements," IEEE Software, vol. 25, no. 2, pp. 34-41, March-April 2008, doi:10.1109/MS.2008.31
Usage of this product signifies your acceptance of the Terms of Use.