Negotiation Constellations – Method Selection Framework for Requirements Negotiation

  • Samuel Fricker
  • Paul Grünbacher
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5025)


Customers, product managers, project leaders, architects, engineers, and other stakeholders are negotiating requirements throughout the software lifecycle. Even-though fundamental for understanding requirements engineer-ing, negotiation has not been as thoroughly studied as other facets of this engineering discipline. This paper casts requirements engineering into the landscape of negotiation by describing a framework for selecting tactics and methods for various negotiation constellations that can be encountered in a software organization. The framework opens perspectives that are essential for understanding the behavior of people involved in development projects, for understanding how development teams and stakeholders create mutually satisfactory solutions, and for giving tactical advice to practitioners.


Requirement Engineering Requirement Engineer Single Party Stakeholder Network Software Organization 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Alexander, I., Robertson, S.: Understanding Project Sociology by Modeling Stakeholders. IEEE Software 21(1), 23–27 (2004)CrossRefGoogle Scholar
  2. 2.
    Boehm, B., Grünbacher, P., Briggs, R.: Developing Groupware for Requirements Negotiation: Lessons Learned. IEEE Software 18(3), 46–55 (2001)CrossRefGoogle Scholar
  3. 3.
    Cechich, A., Piattini, M., Vallecillo, A.: Component-Based Software Quality. LNCS, vol. 2693, pp. 99–127. Springer, Heidelberg (2003)zbMATHGoogle Scholar
  4. 4.
    Cooper, R.: Winning at New Products: Accelerating the Process from Idea to Launch. Perseus Publishing (2001)Google Scholar
  5. 5.
    Curtis, B., Krasner, H., Iscoe, N.: A Field Study of the Software Design Process for Large Systems. Communications of the ACM 31(11), 1268–1287 (1988)CrossRefGoogle Scholar
  6. 6.
    Damian, D., Eberlein, A., Woodward, B., Shaw, M., Gaines, B.: An Empirical Study of Facilitation of Computer-mediated Distributed Requirements Negotiations. In: 5th Intl. Symposium on Requirements Engineering (2001)Google Scholar
  7. 7.
    Doerr, J., Paech, B., Koehler, M.: Requirements Engineering Process Improvement Based on an Information Model. In: 12th IEEE Intl. Requirements Engineering Conference (2004)Google Scholar
  8. 8.
    Foa, U., Foa, E.: Resource Theory of Social Exchange. General Learning Press (1975)Google Scholar
  9. 9.
    Fricker, S., Gorschek, T., Myllyperkiö, P.: Handshaking between Software Projects and Stakeholders Using Implementation Proposals. In: 13th Intl. Working Conference on Requirements Engineering: Foundation for Software Quality (2007)Google Scholar
  10. 10.
    Glinz, M., Wieringa, R. (eds.): IEEE Software Special Issue on Stakeholders in Requirements Engineering 24(2) (2007)Google Scholar
  11. 11.
    Gorschek, T., Svahnberg, M.: Requirements Engineering in Practice: Studies of Six Companies. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 405–426. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  12. 12.
    Grünbacher, P., Seyff, N.: Requirements Negotiation. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 143–162. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  13. 13.
    Humphrey, W., Snyder, T., Willis, R.: Software Process Improvement at Hughes Aircraft. IEEE Software 8(4), 11–23 (1991)CrossRefGoogle Scholar
  14. 14.
    Kotonya, G., Sommerville, I.: Requirements Engineering with Viewpoints. Software Engineering Journal 11(1), 5–18 (1996)CrossRefGoogle Scholar
  15. 15.
    van Lamsweerde, A., Darimont, R., Letier, E.: Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering 24(11), 908–926 (1998)CrossRefGoogle Scholar
  16. 16.
    Lewicki, R., Barry, B., Saunders, D.: Essentials of Negotiation. McGraw-Hill, New York (2007)Google Scholar
  17. 17.
    Lumsdaine, E., Lumsdaine, M.: Creative Problem Solving. IEEE Potentials 13(5), 4–9 (1994)CrossRefGoogle Scholar
  18. 18.
    Marquardt, K.: Patterns for Plug-ins. In: Manolescu, D., Voelter, M., Noble, J. (eds.) Pattern Languages of Program Design 5, pp. 301–336. Addison-Wesley, Reading (2006)Google Scholar
  19. 19.
    Ovaska, P., Rossi, M., Smolander, K.: Filtering, Negotiating and Shifting in the Understanding of Information System Requirements. Scand. J. of Information Systems 17(1), 31–66 (2005)Google Scholar
  20. 20.
    Pohl, K., Böckle, G., van der Linden, F.: Software Product Line Engineering: Foundations, Principles and Techniques. Springer, Heidelberg (2005)zbMATHGoogle Scholar
  21. 21.
    Porter, M.: Competitive Advantage: Creating and Sustaining Superior Performance. The Free Press (1985)Google Scholar
  22. 22.
    Poston, R.: Software Standards. IEEE Software 1(2), 87–94 (1984)CrossRefGoogle Scholar
  23. 23.
    Rahim, M.: Rahim Organizational Conflict Inventories: Professional Manual. Consulting Psychologists Press (1990)Google Scholar
  24. 24.
    Raiffa, H., Richardson, J., Metcalfe, D.: Negotiation Analysis: The Science and Art of Collaborative Decision Making. The Belknap Press of Harvard University Press (2007)Google Scholar
  25. 25.
    Regnell, B., Brinkkemper, S.: Market-Driven Requirements Engineering for Software Products. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 287–308. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  26. 26.
    Robinson, W., Volkov, S.: Supporting the Negotiation Life Cycle. Communications of ACM 41(5), 95–102 (1998)CrossRefGoogle Scholar
  27. 27.
    Rubin, J., Pruitt, D., Kim, S.: Social Conflict: Escalation, Stalemate and Settlement. McGraw-Hill, New York (1994)Google Scholar
  28. 28.
    Schneider, K., von Hunnius, J., Basili, V.: Experience in Implementing a Learning Software Organization. IEEE Software 19(3), 46–49 (2002)CrossRefGoogle Scholar
  29. 29.
    Sommerville, I., Sawyer, P.: Requirements Engineering: A Good Practice Guide. Wiley, Chichester (1997)zbMATHGoogle Scholar
  30. 30.
    Thomas, K.: Conflict and Conflict Management. In: Dunette, M. (ed.) Handbook of Industrial and Organizational Psychology, pp. 889–935. Rand McNally College Publishing Company (1976)Google Scholar
  31. 31.
    Thompson, L.: The Mind and Heart of the Negotiator. Pearson Prentice Hall, London (2005)Google Scholar
  32. 32.
    van de Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., Bijlsma, L.: Towards a Reference Framework for Software Product Management. In: 14th IEEE Intl. Requirements Engineering Conference (2006)Google Scholar
  33. 33.
    Yu, E.: Towards Modelling and Reasoning Support for Early-Phase Requirements Engineering. In: 3rd IEEE Intl. Symposium on Requirements Engineering (1997)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Samuel Fricker
    • 1
    • 2
  • Paul Grünbacher
    • 3
  1. 1.Department of InformaticsUniversity of ZurichZurichSwitzerland
  2. 2.ABB Switzerland Ltd., Power SystemsBadenSwitzerland
  3. 3.Institute for Systems Engineering and AutomationJohannes Kepler Universität (JKU)LinzAustria

Personalised recommendations