by Barry W. Boehm, Alexander Egyed
Abstract:
Negotiating requirements is one of the first steps in any software system life cycle, but its results have probably the most significant impact on the system's value. However, the processes of requirements negotiation are not well understood. We have had the opportunity to capture and analyze requirements negotiation behavior for groups of projects developing library multimedia archive systems, using an instrumented version of the USC WinWin groupware system for requirements negotiation. Some of the more illuminating results were: • Most stakeholder Win Conditions were noncontroversial (were not involved in Issues) • Negotiation activity varied by stakeholder role. • LCO package quality (measured by grading criteria) could be predicted by negotiation attributes. • WinWin increased cooperativeness, reduced friction, and helped focus on key issues.
Reference:
Software Requirements Negotiation: Some Lessons Learned. (Barry W. Boehm, Alexander Egyed), In Proceedings of the 20th International Conference on Software Engineering (ICSE 1998), Kyoto, Japan, 1998.
Bibtex Entry:
@Conference{DBLP:conf/icse/BoehmE98,
author = {Barry W. Boehm and Alexander Egyed},
title = {Software Requirements Negotiation: Some Lessons Learned.},
booktitle = {Proceedings of the 20th International Conference on Software Engineering (ICSE 1998), Kyoto, Japan},
year = {1998},
pages = {503-506},
abstract = {Negotiating requirements is one of the first steps in any software
system life cycle, but its results have probably the most significant
impact on the system's value. However, the processes of requirements
negotiation are not well understood. We have had the opportunity
to capture and analyze requirements negotiation behavior for groups
of projects developing library multimedia archive systems, using
an instrumented version of the USC WinWin groupware system for requirements
negotiation. Some of the more illuminating results were:
• Most stakeholder Win Conditions were noncontroversial (were not
involved in Issues) • Negotiation activity varied by stakeholder
role. • LCO package quality (measured by grading criteria) could
be predicted by negotiation attributes. • WinWin increased cooperativeness,
reduced friction, and helped focus on key issues.},
file = {:Conferences\\ICSE 1998 - Software Requirements Negotiation-Some Lessons Learned\\Software Requirements Negotiation - Some Lessons Learned-preprint.pdf:PDF},
keywords = {},
url = {http://doi.ieeecomputersociety.org/10.1109/ICSE.1998.671616},
}