Using WinWin Quality Requirements Management Tools: A Case Study

Hoh In, Barry W. Boehm

Research output: Contribution to journalArticle

10 Citations (Scopus)

Abstract

Negotiating stakeholder WinWin relationships among software quality requirements is a technique that emerged during the 1990's in order to overcome the difficulties arising from contract-oriented specification compliance (popular in the 1970's) and service-oriented customer satisfaction (popular in the 1980's). Obstacles to adoption of negotiated win-win relationships include coordination of multiple stakeholder interests and priorities, reasoning of complicated dependencies, and scalability of an exponentially increasing resolution option space. Conflict identification and resolution techniques are key success factors to overcome the obstacles. This paper describes two exploratory knowledge-based tools (called "QARCC" and "S-COST")* for conflict identification and resolution and how they were used in the digital library projects of a USC Software Engineering class during the 1996/97 school year. A comparative analysis with the artifacts surfaced by stakeholders and the artifacts generated and analyzed by QARCC and S-COST focused on the conflict resolution process, stakeholders' roles and their relationships to quality artifacts, and tool effectiveness. We conclude that the tools helped stakeholders: (1) surface and negotiate conflicts; (2) identify conflicts among functional and quality requirements; and (3) generate, visualize, and negotiate potential resolution options for the conflicts.

Original languageEnglish
Pages (from-to)141-174
Number of pages34
JournalAnnals of Software Engineering
Volume11
Issue number1
DOIs
Publication statusPublished - 2001
Externally publishedYes

Keywords

  • Conflict identification and resolution
  • Quality assurance
  • Quality requirements negotiation
  • Requirements engineering

ASJC Scopus subject areas

  • Software
  • Computer Graphics and Computer-Aided Design

Fingerprint Dive into the research topics of 'Using WinWin Quality Requirements Management Tools: A Case Study'. Together they form a unique fingerprint.

  • Cite this