Sciweavers

184 search results - page 3 / 37
» Software Requirements Negotiation: Some Lessons Learned
Sort
View
EWCBR
2000
Springer
13 years 9 months ago
Active Delivery for Lessons Learned Systems
Lessons learned processes, and software systems that support them, have been developed by many organizations (e.g., all USA military branches, NASA, several Department of Energy or...
Rosina Weber, David W. Aha, Héctor Mu&ntild...
RE
2004
Springer
13 years 11 months ago
The Conundrum of Categorising Requirements: Managing Requirements for Learning on the Move
This paper reports on our experience of eliciting and managing requirements on a large European-based multinational project, whose purpose is to create a system to support learnin...
Debra Trusso Haley, Bashar Nuseibeh, Helen C. Shar...
CIA
1998
Springer
13 years 10 months ago
Cooperative vs. Competitive Multi-Agent Negotiations in Retail Electronic Commerce
A key lesson learned from economic and game theory research is that negotiation protocols have substantial, rippling effects on the overall nature of the system. online auctions a...
Robert H. Guttman, Pattie Maes
CASCON
2006
100views Education» more  CASCON 2006»
13 years 7 months ago
Software architects in practice: handling requirements
Software architecture can be a critical factor in software development. Understanding what software architects do in practice is necessary to the enterprise of providing technique...
Vidya Lakshminarayanan, WenQian Liu, Charles L. Ch...
HICSS
2002
IEEE
80views Biometrics» more  HICSS 2002»
13 years 10 months ago
EasyWinWin: Managing Complexity in Requirements Negotiation with GSS
More than ¾ of large software projects suffer large cost and schedule overruns or fail outright. Deficits in project requirements cause more than half of these failures and overr...
Robert O. Briggs, Paul Grünbacher