Identifying Quality-Requirement Conflicts

  • Authors:
  • Barry Boehm;Hoh In

  • Affiliations:
  • -;-

  • Venue:
  • IEEE Software
  • Year:
  • 1996

Quantified Score

Hi-index 0.00

Visualization

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.