The importance of IS stakeholder perspectives and perceptions to requirements negotiation

Project managers and developers need to acknowledge the influence of IS stakeholders’ perspectives and perceptions on the outcome of requirements negotiation - the essential component of requirements elicitation. This paper describes a conceptual study, which demonstrates such an influence and asserts that stakeholder perspectives, goals and issues are the key to negotiators’ perceptions of the system requirements. Analysis of two seminal IS case studies further supports this assertion and indicates that goals, perspectives and prior experience with negotiation techniques can guide stakeholders bargaining behaviour during requirements negotiation. Our findings also show that to achieve consensus on requirements, stakeholder perspectives must be aligned or accepted by negotiating parties. Achieving alignment of perspectives, however, is quite difficult because during requirements elicitation stakeholders’ goals continually alter due to their acquisition of technical and business knowledge, development of inter-personal relationships and creation of new perceptions of issues relevant to requirements negotiation.

[1]  Rick Kazman,et al.  From requirements negotiation to software architecture decisions , 2005, Inf. Softw. Technol..

[2]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[3]  A. Finkelstein Report of the Inquiry into the London Ambulance Service , 1993 .

[4]  Jennie Carroll,et al.  Modelling the Requirements Process: where are the people? , 2002 .

[5]  Rick L. Edgeman,et al.  Six sigma seen as a methodology for total quality management , 2001 .

[6]  Jiju Antony,et al.  Some pros and cons of six sigma: an academic perspective , 2004 .

[7]  Max H. Bazerman,et al.  Negotiation in Small Groups , 1989 .

[8]  Pedro Antunes,et al.  Software Requirements Negotiation Using the Software Quality Function Deployment , 2005, CRIWG.

[9]  L. Porter The negotiation process: Theories and applications. , 1979 .

[10]  Axel van Lamsweerde,et al.  Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[11]  Israel Borovits,et al.  Group processes and the development of information systems: A social psychological perspective , 1990, Inf. Manag..

[12]  Stefan Biffl,et al.  Supporting Decision-Making in Software Engineering with Process Simulation and Empirical Studies , 2003, Int. J. Softw. Eng. Knowl. Eng..

[13]  S. Easterbrook,et al.  A Survey of Empirical Studies of Conflict , 1993 .

[14]  Walker Royce Software Project Management , 1998 .

[15]  Steve Easterbrook Negotiation and the Role of the Requirements Specification 1 , 1993 .

[16]  Paul A. Swatman,et al.  Managing the RE Process : Lessons from Commercial Practice , 1999 .

[17]  Dietmar Pfahl,et al.  Quantitative WinWin: a new method for decision support in requirements negotiation , 2002, SEKE '02.

[18]  Johan F. Hoorn,et al.  Requirements change: Fears dictate the must haves; desires the won't haves , 2007, J. Syst. Softw..

[19]  Steve M. Easterbrook,et al.  Elicitation of requirements from multiple perspectives , 1991 .

[20]  Meir M. Lehman,et al.  Laws of Software Evolution Revisited , 1996, EWSPT.

[21]  Sten Carlsson Information Systems Development : Participation And Intersubjectivity - Is This Just A Matter Of Communication? , 2002, ECIS.

[22]  Michael Newman,et al.  SOCRATE: An Implementation Debacle , 1996, ECIS.

[23]  Barry W. Boehm,et al.  Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..

[24]  Igor T. Hawryszkiewycz,et al.  Introduction to systems analysis and design , 1988 .

[25]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[26]  A. van Lamsweerde Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004 .

[27]  Jacob L. Cybulski,et al.  Consensus Making in Requirements Negotiation: the communication perspective , 2005, Australas. J. Inf. Syst..

[28]  Guy Fitzgerald,et al.  Negotiating and Understanding Information Systems Requirements: The Use of Set Diagrams , 2000, Requirements Engineering.

[29]  Jeswald W. Salacuse,et al.  Ten Ways that Culture Affects Negotiating Style: Some Survey Results , 1998 .

[30]  M. Morris,et al.  Rapport in conflict resolution: Accounting for how face-to-face contact fosters mutual cooperation in mixed-motive conflicts. , 2000 .

[31]  Steve Easterbrook,et al.  Resolving requirements conflicts with computer-supported negotiation , 1994 .

[32]  Bart J. Wilson,et al.  A Comparison of Auctions and Multilateral Negotiations , 2002 .

[33]  Mark Lycett,et al.  Communication issues in requirements elicitation: a content analysis of stakeholder experiences , 2003, Inf. Softw. Technol..

[34]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[35]  Katia Sycara,et al.  Bilateral negotiation decisions with uncertain dynamic outside options , 2004 .

[36]  Ross A. Malaga,et al.  A weighted sum genetic algorithm to support multiple-party multiple-objective negotiations , 2002, IEEE Trans. Evol. Comput..

[37]  L. Thompson,et al.  A Look into the Mind of the Negotiator: Mental Models in Negotiation , 2003 .

[38]  Richard P. Larrick,et al.  Thinking of others : How perspective taking changes negotiators' aspirations and fairness perceptions as a function of negotiator relationships , 1998 .

[39]  A. V. Lamsweerde,et al.  Agent-based tactics for goal-oriented requirements elaboration , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.

[40]  Claes Wohlin,et al.  The fundamental nature of requirements engineering activities as a decision-making process , 2003, Inf. Softw. Technol..

[41]  J. Cybulski,et al.  Stakeholder bargaining behaviour : the social backbone of communication, negotiation and consensus as used for information system requirements elicitation , 2005 .

[42]  Kathy Schwalbe,et al.  Information Technology Project Management , 1999 .

[43]  Philip L. Smith,et al.  SOCIAL MOTIVES IN NEGOTIATION: THE RELATIONSHIPS BETWEEN DYAD COMPOSITION, NEGOTIATION PROCESSES AND OUTCOMES , 2003 .

[44]  Yasuhiro Mashiko,et al.  Using the GQM Paradigm to Investigate Influential Factors for Software Process Improvement , 1997, J. Syst. Softw..

[45]  Jeff M. Bickerton,et al.  Getting to Yes: Negotiating Agreement without Giving in , 2002 .

[46]  Nathalie N. Mitev,et al.  Understanding Information System Failures from the Complexity Perspective , 2008 .

[47]  M. Abdollahian,et al.  Modeling the Strategic Effects of Risk and Perceptions in Linkage Politics , 2003 .