The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.02 - March (1996 vol.13)
pp: 25-35
ABSTRACT
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, "Identifying Quality-Requirement Conflicts", IEEE Software, vol.13, no. 2, pp. 25-35, March 1996, doi:10.1109/52.506460
29 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool