WinWin Spiral Model 
 

Introduction
Research Sponsors
WinWin Downloads (Software and Documentation)
WinWin Web-based Software
Publications
For Further Information
CSE Home Page




Introduction

The WinWin Spiral Model uses Theory W (win-win) to develop software and system requirements, and architectural solutions, as win conditions negotiated among a project's stakeholders (user, customer, developer, maintainer, interfacer, etc.). The WinWin negotiation tool is a Unix workstation-based groupware support system that allows stakeholders to enter win conditions, explore their interactions, and negotiate mutual agreements on the specifics of the new project being contracted. The model and support system also feature a central role for quantitative tradeoff analysis tools such as COCOMO®.

 


Research Sponsors

In addition to the on-going support provided by the USC-CSE Affiliates, the Center is under contract to the Defense Advanced Research Projects Agency (DARPA), via the Air Force Research Laboratory (formerly known as Rome Laboratory), to develop in collaboration with The Aerospace Corporation, a robust version of the WinWin system and to apply it in the domain of Satellite Ground Stations (SGSs). 


WinWin Downloads (Software and Documentation)

The USC software implementations of WinWin have been developed by graduate student programming teams under the leadership of Dr. Ellis Horowitz. The tool is available for Sun Sparc workstations runnng Unix, personal computers running Linux, and Java-enabled environments. The program files download in compressed format and need to be unzipped with the appropriate utility.

WinWin Release 2.0:

Java WinWin Release 1.2:

Documentation:


WinWin Web-based Software

For Netscape Navigator 4.x, or Microsoft Internet Explorer 4.x:

 

If you experience problems with Java WinWin, run it with debug:


Publications

To view the documents you may need PDF Acrobat Viewer or a Postscript Viewer:
  1. Boehm, B., Egyed, A., Kwan, J., Port, D., Shah, A., and Madachy, R., "Using  the WinWin Spiral Model: A Case Study", IEEE Computer, July 1998, pp. 33-44 [PDF]
  2. Boehm, B., Egyed, A., Port, D., Shah, A., Kwan, J., Madachy, R., "A Stakeholder Win-Win Approach to Software Engineering Education", Annals of Software Engineering, January 1999. [PDF]
  3. Boehm, B., Egyed, A., "Optimizing Software Product Integrity through Life-Cycle Process Integration", Journal for Computer Standards and Interfaces, 1999 [PDF]
  4. Egyed, A., Boehm, B. "Comparing Software System Requirements Negotiation Patterns", to appear in Journal for Systems Engineering, 1999. [PDF]
  5. Boehm, B. and Egyed, A., "Software Requirements Negotiation: Some Lessons Learned," Proceedings of the 20th International Conference on Software Engineering, April 1998. [PDF]
  6. Egyed A. and Boehm, B., "Telecooperation Experience with the WinWin System," Proceedings of the 15th IFIP World Computer Congress, September 1998. [PDF]
  7. Egyed, A. and Boehm, B., "A Comparison Study in Software Requirements Negotiation," Proceedings of the International Conferences of Systems Engineering (INCOSE), July 1998. [PDF]
  8. Egyed, A. and Boehm, B., "Analysis of Software Requirements Negotiation Behavior Patterns," Proceedings of the International Conferences of Systems Engineering (INCOSE), July 1997. [PDF]
  9. Boehm, B., Egyed, A., Kwan, J., Madachy, R., "Developing Multimedia Applications with the WinWin Spiral Model," Proceedings of the ESEC/FSE 97, 1997. [PDF]
  10. Boehm, B. and Egyed, A., "WinWin Requirements Negotiation Processes: A Multi-Project Analysis," Proceedings of 5th International Conference on Software Processes, June 1998. [PDF]
  11. Boehm, B. and Egyed, A., "Improving the Life-Cycle Process in Software Engineering Education," Proceedings of European Software Day (as part of the 24th Euromicro conference), August 1998. [PDF]
  12. B. Boehm and H. In, "Aids for Identifying Conflicts Among Quality Requirements," One of best papers at International Conference on Requirements Engineering (ICRE96), Colorado, April 1996, and IEEE Software, March 1996
  13. P. Bose, "Conceptual Design Model based Requirements Analysis in the WinWin Framework for Concurrent Requirements Engineering", IWSSD, 1995
  14. P. Bose, "A Model for Decision Maintenance in the WinWin Collaboration Framework", Knowledge Based Software Engineering (KBSE '95), 1995
  15. B. Boehm, P. Bose, E. Horowitz, and M. J. Lee, "Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach," Proceedings of the 17th International Conference on Software Engineering (ICSE-17), Seattle, April 1995.
  16. M. J. Lee, "Formally Modeling the WinWin Requirements Negotiation System," Doctoral Consortium, Second IEEE International Symposium on Requirements Engineering (RE'95), York, March 1995.
  17. M. J. Lee, and Barry Boehm, Knowledge Summary: USC Center for Software Engineering Focused Workshop on Next Generation Software Processes and Their Support, USC Center for Software Engineering, 1994.
  18. B. Boehm and P. Bose, "A Collaborative Spiral Software Process Model Based on Theoy W", Third International Conference on the Software Process, 1994.
  19. B. Boehm, P. Bose, E. Horowitz, and M. J. Lee, "Experimental Results from a Prototype Next-Generation Process Support System," TRW Systems Integration Group Technology Review, Summer 1994, Volume 2, Number 1.
  20. B. Boehm, P. Bose, E. Horowitz and M. J. Lee, "Software Requirements As Negotiated Win Conditions," Proceedings of the First International Conference on Requirements Engineering(ICRE94), IEEE Computer Society Press, Colorado Springs Colorado, April 1994.


For Further Information Please Contact:

Center for Software Engineering
Salvatori Hall Room 328
University of Southern California
941 W. 37th Place
Los Angeles, CA 90089-0781

Voice: (213) 740-6506
Fax: (213) 740-4927
E-mail:
hkitapci@sunset.usc.edu


Click on the graph to view website visitor statistics:

  To the Center for Software Engineering Home Page

Copyright 1995-2002 The University of Southern California

The written material, text, graphics, and software available on this page and all related pages may be copied, used, and distributed freely as long as the University of Southern California as the source of the material, text, graphics or software is always clearly indicated and such acknowledgement always accompanies any reuse or redistribution of the material, text, graphics or software; also permission to use the material, text, graphics or software on these pages does not include the right to repackage the material, text, graphics or software in any form or manner and then claim exclusive proprietary ownership of it as part of a commercial offering of services or as part of a commercially offered product.