Requirements engineering, expectations management, and the Two Cultures

One of the difficulties in requirements negotiation is to determine a feasible and mutually satisfactory set of requirements for the developer and the user, a problem related to C.P. Snow's (1959) "Two Cultures" problem. During the last year of our experience with an annual series of digital library projects, we have been experimenting with expectations management and domain specific lists of "simplifiers" and "complicators", as a way to address the "Two Cultures" problem involving librarians and computer scientists. Initial results indicate that the simplifiers and complicators approach successfully reduced the number of projects having serious feasibility problems, and helped manage the expectations of both the developers and the customers/users. We see no obstacles to applying the approach to other domains.

[1]  Bashar Nuseibeh,et al.  Viewpoints: A Framework for Integrating Multiple Perspectives in System Development , 1992, Int. J. Softw. Eng. Knowl. Eng..

[2]  Barry W. Boehm,et al.  Using the WinWin Spiral Model: A Case Study , 1998, Computer.

[3]  John Mylopoulos,et al.  Understanding "why" in software process modelling, analysis, and design , 1994, Proceedings of 16th International Conference on Software Engineering.

[4]  Barry Boehm,et al.  Developing multimedia applications with the WinWin spiral model , 1997, ESEC '97/FSE-5.

[5]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[6]  Barry W. Boehm,et al.  Software requirements as negotiated win conditions , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[7]  Jerry Fisher,et al.  From the Editor: Model-Based Systems Engineering: A New Paradigm , 1998 .

[8]  W. Blatchford Getting a yes.... , 1992, Journal of the California Dental Association.

[9]  W. L. Sumner The Two Cultures and the Scientific Revolution , 1959, Nature.

[10]  Barry W. Boehm,et al.  Escaping the software tar pit: model clashes and how to avoid them , 1999, SOEN.

[11]  Walker Royce,et al.  Software Project Management: A Unified Framework , 1998 .

[12]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[13]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[14]  Stephen Fickas,et al.  Goal-directed concept acquisition in requirements elicitation , 1991, Proceedings of the Sixth International Workshop on Software Specification and Design.

[15]  Barry W. Boehm,et al.  Anchoring the Software Process , 1996, IEEE Softw..

[16]  Julie Johnson What is the Rational Unified Process ? , 1999 .

[17]  Anthony Gargaro,et al.  Transitioning a model-based software engineering architectural style to Ada 95 , 1995, TRI-Ada '95.

[18]  Naomi Karten,et al.  Managing expectations , 2015, Veterinary Record.

[19]  Erran Carmel,et al.  PD and joint application design: a transatlantic comparison , 1993, CACM.