One of the biggest risks in software requirements engineering is the
risk of overemphasizing one quality attribute requirement (e.g.,
performance) at the expense of others at least as important (e.g.,
evolvability and portability). The paper describes an exploratory
knowledge based tool for identifying potential conflicts among quality
attributes early in the software/ system life cycle. The Quality
Attribute Risk and Conflict Consultant (QARCC) examines the quality
attribute tradeoffs involved in software architecture and process
strategies. It operates in the context of the USC CSE WinWin system,
a groupware support system for determining software and system requirements
as negotiated win conditions. We have developed and experimented
with an initial QARCC 1 prototype. We are using the results of the
experiment to develop an improved QARCC 2 tool. From our initial
experimentation, we concluded that QARCC can alert users, developers,
customers, and other stakeholders to conflicts among their software
quality requirements and can help them identify additional, potentially
important quality requirements. We also concluded that QARCC needs
further refinement to avoid overloading users with insignificant
quality conflict suggestions. We are now refining the knowledge base
to address more detailed quality attributes in a more selective fashion
%0 Journal Article
%1 boehm:ieeesw96
%A Boehm, Barry
%A In, Hoh
%C Los Alamitos, CA, USA
%D 1996
%I IEEE Computer Society Press
%J IEEE Software
%K Attributes Quality
%N 2
%P 25--35
%R http://dx.doi.org/10.1109/52.506460
%T Identifying Quality-Requirement Conflicts
%U http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=506460
%V 13
%X One of the biggest risks in software requirements engineering is the
risk of overemphasizing one quality attribute requirement (e.g.,
performance) at the expense of others at least as important (e.g.,
evolvability and portability). The paper describes an exploratory
knowledge based tool for identifying potential conflicts among quality
attributes early in the software/ system life cycle. The Quality
Attribute Risk and Conflict Consultant (QARCC) examines the quality
attribute tradeoffs involved in software architecture and process
strategies. It operates in the context of the USC CSE WinWin system,
a groupware support system for determining software and system requirements
as negotiated win conditions. We have developed and experimented
with an initial QARCC 1 prototype. We are using the results of the
experiment to develop an improved QARCC 2 tool. From our initial
experimentation, we concluded that QARCC can alert users, developers,
customers, and other stakeholders to conflicts among their software
quality requirements and can help them identify additional, potentially
important quality requirements. We also concluded that QARCC needs
further refinement to avoid overloading users with insignificant
quality conflict suggestions. We are now refining the knowledge base
to address more detailed quality attributes in a more selective fashion
@article{boehm:ieeesw96,
abstract = {One of the biggest risks in software requirements engineering is the
risk of overemphasizing one quality attribute requirement (e.g.,
performance) at the expense of others at least as important (e.g.,
evolvability and portability). The paper describes an exploratory
knowledge based tool for identifying potential conflicts among quality
attributes early in the software/ system life cycle. The Quality
Attribute Risk and Conflict Consultant (QARCC) examines the quality
attribute tradeoffs involved in software architecture and process
strategies. It operates in the context of the USC CSE WinWin system,
a groupware support system for determining software and system requirements
as negotiated win conditions. We have developed and experimented
with an initial QARCC 1 prototype. We are using the results of the
experiment to develop an improved QARCC 2 tool. From our initial
experimentation, we concluded that QARCC can alert users, developers,
customers, and other stakeholders to conflicts among their software
quality requirements and can help them identify additional, potentially
important quality requirements. We also concluded that QARCC needs
further refinement to avoid overloading users with insignificant
quality conflict suggestions. We are now refining the knowledge base
to address more detailed quality attributes in a more selective fashion},
added-at = {2007-04-15T04:42:29.000+0200},
address = {Los Alamitos, CA, USA},
author = {Boehm, Barry and In, Hoh},
biburl = {https://www.bibsonomy.org/bibtex/2a7ced94e3c325e3a0f1fe2fc15129934/piveta},
description = {Teste},
doi = {http://dx.doi.org/10.1109/52.506460},
interhash = {917d79c314520f2813138070139e1604},
intrahash = {a7ced94e3c325e3a0f1fe2fc15129934},
issn = {0740-7459},
journal = {IEEE Software},
keywords = {Attributes Quality},
number = 2,
owner = {Eduardo Piveta},
pages = {25--35},
pdf = {http://courses.cs.tamu.edu/cpsc689/hohin/cpsc608/notes/icre96v5.5.pdf},
publisher = {IEEE Computer Society Press},
timestamp = {2007-04-15T04:46:20.000+0200},
title = {Identifying Quality-Requirement Conflicts},
url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=506460},
volume = 13,
year = 1996
}