Developing groupware for requirements negotiation: lessons learned
- 1 May 2001
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 18 (3) , 46-55
Abstract
Defining requirements is a complex and difficult process, and defects in the process often lead to costly project failures. There is no complete and well-defined set of requirements waiting to be discovered in system development. Different stakeholders: users, customers, managers, domain experts, and developers, come to the project with diverse expectations and interests. Requirements emerge in a highly collaborative, interactive, and interdisciplinary negotiation process that involves heterogeneous stakeholders. At the University of Southern California's Center for Software Engineering, we have developed a series of groupware implementations for the WinWin requirements negotiation approach. The WinWin approach involves having a system's success-critical stakeholders participate in a negotiation process so they can converge on a mutually satisfactory or win-win set of requirements. The WinWin groupware system, which has evolved over four generations, enables and facilitates heterogeneous stakeholder participation and collaboration. Each generation reflects an increase in our understanding of what is needed for successful WinWin groupware operations and technology support. The authors present the major lessons they learned during WinWin's development.Keywords
This publication has 10 references indexed in Scilit:
- Software requirements as negotiated win conditions2002
- Collaborative requirements negotiation with EasyWinWin2002
- Using group support systems for software inspectionsIEEE Software, 2001
- Requirements that handle IKIWISI, COTS, and rapid changeComputer, 2000
- Comparing software system requirements negotiation patternsSystems Engineering, 1999
- Using the WinWin spiral model: a case studyComputer, 1998
- Lessons from a Dozen Years of Group Support Systems Research: A Discussion of Lab and Field FindingsJournal of Management Information Systems, 1996
- Theory-W software project management principles and examplesIEEE Transactions on Software Engineering, 1989
- The Mythical Man-MonthACM SIGPLAN Notices, 1975
- The Mythical Man-Month1975