2001 · 71 citations · 13 references
ComputingProject ManagementQuality ManagementConflict ResolutionRequirements EngineeringSoftware EngineeringInformation Systems Project ManagementRequirements ManagementRequirements NegotiationSoftware DesignSoftware Project ManagementSoftware Quality AssuranceProcess EffectivenessProject Requirements ManagementRequirements CaptureRequirements Conflict DetectionRequirements Conflict ResolutionResolutions
This paper describes the application of the WinWin paradigm to identify and resolve conflicts in a series of real-client, student-developer digital library projects. The paper is based on a case study of the statistical analysis of 15 projects and an in-depth analysis of one representative project. These analyses focus on the conflict resolution process, stakeholders ’ roles and their relationships to quality artifacts, and tool effectiveness. We show that stakeholders tend to accept satisfactory rather than optimal resolutions. Users and customers are more proactive in stating win conditions, whereas developers are more active in working toward resolutions. Further, we suggest that knowledge-based automated aids have potential to significantly enhance process effectiveness and efficiency. Finally, we conclude that such processes and tools have theoretical and practical implications in the quest for better software requirements elicitation.
13
James A. McCall · Medical Entomology and Zoology · 1977 · 823 citations
Quantitative evaluation of software quality
Barry Boehm, Jonathan R. Brown, M. Lipow · 1976 · 631 citations
SAAM: a method for analyzing the properties of software architectures
Rick Kazman, Len Bass, Gregory D. Abowd et al. · 1994 · 484 citations