Developing groupware for requirements negotiation: lessons learned
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, an...
Gespeichert in:
Veröffentlicht in: | IEEE software 2001-05, Vol.18 (3), p.46-55 |
---|---|
Hauptverfasser: | , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 55 |
---|---|
container_issue | 3 |
container_start_page | 46 |
container_title | IEEE software |
container_volume | 18 |
creator | Boehm, B. Grunbacher, P. Briggs, R.O. |
description | 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. |
doi_str_mv | 10.1109/52.922725 |
format | Article |
fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_proquest_journals_215829351</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>922725</ieee_id><sourcerecordid>914665735</sourcerecordid><originalsourceid>FETCH-LOGICAL-c338t-8691ae25ea52aa985417003d18b1e15098086eaa23336afb3c82983d0836eb523</originalsourceid><addsrcrecordid>eNp90D1PwzAQBmALgUQpDKxMEQOIIeXsixObDcqnVIkFZstNL1Wq1G7tBMS_J1UQAwPTDffoPl7GTjlMOAd9LcVEC1EIucdGXGORZlxn-2wERQZpkUl9yI5iXAGA5AgjdndPH9T4Te2WyTL4bvNpAyWVD0mgbVcHWpNrY-Jo6dvatrV3N0lDMXoX-2qDo8UxO6hsE-nkp47Z--PD2_Q5nb0-vUxvZ2mJqNpU5ZpbEpKsFNZqJTNeAOCCqzknLkErUDlZKxAxt9UcSyW0wgUozGkuBY7Z5TB3E_y2o9iadR1LahrryHfRaJ7luSxQ9vLiXyn6W5DDDp7_gSvfBdd_YQSX_X7sUxqzqwGVwccYqDKbUK9t-DIczC50I4UZQu_t2WBrIvp1P81vv3p6pw</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>215829351</pqid></control><display><type>article</type><title>Developing groupware for requirements negotiation: lessons learned</title><source>IEEE Electronic Library (IEL)</source><creator>Boehm, B. ; Grunbacher, P. ; Briggs, R.O.</creator><creatorcontrib>Boehm, B. ; Grunbacher, P. ; Briggs, R.O.</creatorcontrib><description>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.</description><identifier>ISSN: 0740-7459</identifier><identifier>EISSN: 1937-4194</identifier><identifier>DOI: 10.1109/52.922725</identifier><identifier>CODEN: IESOEG</identifier><language>eng</language><publisher>Los Alamitos: IEEE</publisher><subject>Collaboration ; Collaborative software ; Collaborative work ; Computer programs ; Contractors ; Costs ; Customers ; Forward contracts ; Groupware ; Information systems ; Interactive ; Negotiations ; Organizational change ; Process planning ; Product development ; Programming ; Project management ; Software ; Software engineering ; Software maintenance ; Southern California ; Stakeholders ; Success</subject><ispartof>IEEE software, 2001-05, Vol.18 (3), p.46-55</ispartof><rights>Copyright Institute of Electrical and Electronics Engineers, Inc. (IEEE) May/Jun 2001</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c338t-8691ae25ea52aa985417003d18b1e15098086eaa23336afb3c82983d0836eb523</citedby><cites>FETCH-LOGICAL-c338t-8691ae25ea52aa985417003d18b1e15098086eaa23336afb3c82983d0836eb523</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/922725$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,780,784,796,27924,27925,54758</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/922725$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Boehm, B.</creatorcontrib><creatorcontrib>Grunbacher, P.</creatorcontrib><creatorcontrib>Briggs, R.O.</creatorcontrib><title>Developing groupware for requirements negotiation: lessons learned</title><title>IEEE software</title><addtitle>S-M</addtitle><description>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.</description><subject>Collaboration</subject><subject>Collaborative software</subject><subject>Collaborative work</subject><subject>Computer programs</subject><subject>Contractors</subject><subject>Costs</subject><subject>Customers</subject><subject>Forward contracts</subject><subject>Groupware</subject><subject>Information systems</subject><subject>Interactive</subject><subject>Negotiations</subject><subject>Organizational change</subject><subject>Process planning</subject><subject>Product development</subject><subject>Programming</subject><subject>Project management</subject><subject>Software</subject><subject>Software engineering</subject><subject>Software maintenance</subject><subject>Southern California</subject><subject>Stakeholders</subject><subject>Success</subject><issn>0740-7459</issn><issn>1937-4194</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2001</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><sourceid>8G5</sourceid><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GNUQQ</sourceid><sourceid>GUQSH</sourceid><sourceid>M2O</sourceid><recordid>eNp90D1PwzAQBmALgUQpDKxMEQOIIeXsixObDcqnVIkFZstNL1Wq1G7tBMS_J1UQAwPTDffoPl7GTjlMOAd9LcVEC1EIucdGXGORZlxn-2wERQZpkUl9yI5iXAGA5AgjdndPH9T4Te2WyTL4bvNpAyWVD0mgbVcHWpNrY-Jo6dvatrV3N0lDMXoX-2qDo8UxO6hsE-nkp47Z--PD2_Q5nb0-vUxvZ2mJqNpU5ZpbEpKsFNZqJTNeAOCCqzknLkErUDlZKxAxt9UcSyW0wgUozGkuBY7Z5TB3E_y2o9iadR1LahrryHfRaJ7luSxQ9vLiXyn6W5DDDp7_gSvfBdd_YQSX_X7sUxqzqwGVwccYqDKbUK9t-DIczC50I4UZQu_t2WBrIvp1P81vv3p6pw</recordid><startdate>20010501</startdate><enddate>20010501</enddate><creator>Boehm, B.</creator><creator>Grunbacher, P.</creator><creator>Briggs, R.O.</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7XB</scope><scope>87Z</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>F~G</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M1Q</scope><scope>M2O</scope><scope>M2P</scope><scope>M2T</scope><scope>M7S</scope><scope>MBDVC</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>7SP</scope><scope>F28</scope><scope>FR3</scope></search><sort><creationdate>20010501</creationdate><title>Developing groupware for requirements negotiation: lessons learned</title><author>Boehm, B. ; Grunbacher, P. ; Briggs, R.O.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c338t-8691ae25ea52aa985417003d18b1e15098086eaa23336afb3c82983d0836eb523</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2001</creationdate><topic>Collaboration</topic><topic>Collaborative software</topic><topic>Collaborative work</topic><topic>Computer programs</topic><topic>Contractors</topic><topic>Costs</topic><topic>Customers</topic><topic>Forward contracts</topic><topic>Groupware</topic><topic>Information systems</topic><topic>Interactive</topic><topic>Negotiations</topic><topic>Organizational change</topic><topic>Process planning</topic><topic>Product development</topic><topic>Programming</topic><topic>Project management</topic><topic>Software</topic><topic>Software engineering</topic><topic>Software maintenance</topic><topic>Southern California</topic><topic>Stakeholders</topic><topic>Success</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Boehm, B.</creatorcontrib><creatorcontrib>Grunbacher, P.</creatorcontrib><creatorcontrib>Briggs, R.O.</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>Access via ABI/INFORM (ProQuest)</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (Alumni Edition)</collection><collection>Military Database (Alumni Edition)</collection><collection>Science Database (Alumni Edition)</collection><collection>Telecommunications (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies & Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>Business Premium Collection (Alumni)</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer Science Database</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing Database</collection><collection>Military Database</collection><collection>Research Library</collection><collection>Science Database</collection><collection>Telecommunications Database</collection><collection>Engineering Database</collection><collection>Research Library (Corporate)</collection><collection>Advanced Technologies & Aerospace Database</collection><collection>ProQuest Advanced Technologies & Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Electronics & Communications Abstracts</collection><collection>ANTE: Abstracts in New Technology & Engineering</collection><collection>Engineering Research Database</collection><jtitle>IEEE software</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Boehm, B.</au><au>Grunbacher, P.</au><au>Briggs, R.O.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Developing groupware for requirements negotiation: lessons learned</atitle><jtitle>IEEE software</jtitle><stitle>S-M</stitle><date>2001-05-01</date><risdate>2001</risdate><volume>18</volume><issue>3</issue><spage>46</spage><epage>55</epage><pages>46-55</pages><issn>0740-7459</issn><eissn>1937-4194</eissn><coden>IESOEG</coden><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.</abstract><cop>Los Alamitos</cop><pub>IEEE</pub><doi>10.1109/52.922725</doi><tpages>10</tpages></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | ISSN: 0740-7459 |
ispartof | IEEE software, 2001-05, Vol.18 (3), p.46-55 |
issn | 0740-7459 1937-4194 |
language | eng |
recordid | cdi_proquest_journals_215829351 |
source | IEEE Electronic Library (IEL) |
subjects | Collaboration Collaborative software Collaborative work Computer programs Contractors Costs Customers Forward contracts Groupware Information systems Interactive Negotiations Organizational change Process planning Product development Programming Project management Software Software engineering Software maintenance Southern California Stakeholders Success |
title | Developing groupware for requirements negotiation: lessons learned |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-25T18%3A34%3A47IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Developing%20groupware%20for%20requirements%20negotiation:%20lessons%20learned&rft.jtitle=IEEE%20software&rft.au=Boehm,%20B.&rft.date=2001-05-01&rft.volume=18&rft.issue=3&rft.spage=46&rft.epage=55&rft.pages=46-55&rft.issn=0740-7459&rft.eissn=1937-4194&rft.coden=IESOEG&rft_id=info:doi/10.1109/52.922725&rft_dat=%3Cproquest_RIE%3E914665735%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=215829351&rft_id=info:pmid/&rft_ieee_id=922725&rfr_iscdi=true |