loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Identifying Quality-Requirement Conflicts
March 1996 (vol. 13 no. 2)
pp. 25-35
ASCII Text
x 
 
Barry Boehm, Hoh In, "Identifying Quality-Requirement Conflicts," IEEE Software, vol. 13, no. 2, pp. 25-35, March, 1996.
 
 
BibTex
x
 
@article{ 10.1109/52.506460,
author = {Barry Boehm and Hoh In},
title = {Identifying Quality-Requirement Conflicts},
journal ={IEEE Software},
volume = {13},
number = {2},
issn = {0740-7459},
year = {1996},
pages = {25-35},
doi = {http://doi.ieeecomputersociety.org/10.1109/52.506460},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Identifying Quality-Requirement Conflicts
IS - 2
SN - 0740-7459
SP25
EP35
EPD - 25-35
A1 - Barry Boehm,
A1 - Hoh In,
PY - 1996
VL - 13
JA - IEEE Software
ER -
 
Despite well-specified functional and interface requirements, many software projects have failed because they had a poor set of quality-attribute requirements. To find the right balance of quality-attribute requirements, you must identify the conflicts among desired quality attributes and work out a balance of attribute satisfaction. We have developed The Quality Attribute Risk and Conflict Consultant, a knowledge-based tool that can be used early in the system life cycle to identify potential conflicts. QARCC operates in the context of the WinWin system, a groupware support system that determines software and system requirements as negotiated win conditions. This article summarizes our experiences developing the QARCC-1 prototype using an early version of WinWin, and our integration of the resulting improvements into QARCC-2.
Citation:
Barry Boehm, Hoh In, "Identifying Quality-Requirement Conflicts," IEEE Software, vol. 13, no. 2, pp. 25-35, Mar. 1996, doi:10.1109/52.506460
Usage of this product signifies your acceptance of the Terms of Use.