What This Document Is
This report details research and development concerning collaborative software – specifically, “groupware” – designed to improve the process of gathering and finalizing system requirements. It focuses on a methodology called “WinWin,” intended to facilitate negotiation among diverse stakeholders involved in software projects. The work originates from the University of Southern California’s Center for Software Engineering and represents an evolution through multiple generations of system implementations. It’s a technical report outlining practical experiences and lessons learned in building tools to support complex, interactive requirements definition.
Why This Document Matters
This report is valuable for software engineering students, practicing software professionals, and researchers interested in the human and social aspects of software development. It’s particularly relevant for those involved in large-scale projects with numerous stakeholders, or those seeking to understand how to mitigate risks associated with poorly defined requirements. Project managers, systems analysts, and anyone exploring collaborative development techniques will find insights into the challenges and potential benefits of groupware-supported negotiation. Understanding these concepts can lead to more successful project outcomes and improved stakeholder satisfaction.
Common Limitations or Challenges
This report is a retrospective analysis of a specific research effort. It does not offer a universal “how-to” guide for requirements engineering or groupware implementation. It focuses on the experiences with the WinWin approach and may not directly translate to all project contexts or methodologies. The report details challenges encountered, but doesn’t provide pre-packaged solutions or guarantee success in replicating the results. It’s a deep dive into a specific case study, not a broad overview of all available tools or techniques.
What This Document Provides
* An overview of the WinWin requirements negotiation approach.
* A historical account of the development of a WinWin groupware system across multiple iterations.
* Identification of key challenges in supporting collaborative requirements negotiation with technology.
* Insights into the importance of stakeholder heterogeneity and its impact on system design.
* Lessons learned regarding the practical application of group dynamics principles in software engineering.
* A discussion of the difficulties in achieving shared understanding and commitment among distributed teams.