Managing Requirements Engineering Risks: An Analysis and Synthesis of the Literature

Requirements engineering is recognized as a key discipline in developing business software. Practitioners are, however, facing a steady stream of new techniques and an increasingly differentiated portfolio of requirements engineering risks. The purpose of this paper is to propose a model that links the available repertoire of techniques to the situations in which practitioners find themselves. To this end, the paper reviews the software development and requirements engineering literature to understand the risks that characterize requirement engineering situations, to classify available techniques to resolve these risks, and to identify key principles by which tactics can be applied to resolve requirements risks. The paper synthesizes the findings from the analysis into a contingency model for managing requirements engineering risks. The model sets the scene for future research and practitioners can use it to navigate the requirements engineering landscape.

[1]  Alan R. Hevner,et al.  Box-structured requirements determination methods , 1995, Decis. Support Syst..

[2]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[3]  David W. Conrath,et al.  The Use of Cognitive Mapping for Information Requirements Analysis , 1986, MIS Q..

[4]  Justus D. Naumann,et al.  Empirical investigation of systems development practices and results , 1984, Inf. Manag..

[5]  Joyce J. Elam,et al.  Semantic Structuring in Analyst Acquisition and Representation of Facts in Requirements Analysis , 1998, Inf. Syst. Res..

[6]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[7]  Henry Mintzberg,et al.  Structure in Fives: Designing Effective Organizations , 1983 .

[8]  Christian S. Jensen,et al.  A foundation for capturing and querying complex multidimensional data , 2001, Inf. Syst..

[9]  B. Boehm Software risk management: principles and practices , 1991, IEEE Software.

[10]  Kalle Lyytinen,et al.  Expectation failure concept and systems analysts' view of information system failures: Results of an exploratory study , 1988, Inf. Manag..

[11]  Evan W. Duggan,et al.  Integrating nominal group technique and joint application development for improved systems requirements determination , 2004, Inf. Manag..

[12]  J. Livari,et al.  The organizational fit of information systems , 1992 .

[13]  Shih-Chien Chou,et al.  Consistency management in a process environment , 1999, J. Syst. Softw..

[14]  Graeme G. Shanks,et al.  User viewpoint modelling: understanding and representing user viewpoints during requirements definition , 1997, Inf. Syst. J..

[15]  Kalle Lyytinen,et al.  A Framework for software risk management , 1996, Scand. J. Inf. Syst..

[16]  Linda A. Macaulay,et al.  Requirements capture and IS methodologies , 1996, Inf. Syst. J..

[17]  Erran Carmel,et al.  Customer-developer links in software development , 1995, CACM.

[18]  Gary D. Scudder,et al.  Improving Speed and Productivity of Software Development: A Global Survey of Software Developers , 1996, IEEE Trans. Software Eng..

[19]  Venkataraman Ramesh,et al.  Expressing casual relationships in conceptual database schemas , 1999, J. Syst. Softw..

[20]  Soongoo Hong,et al.  Objective quality ranking of computing journals , 2003, CACM.

[21]  Jan Stage,et al.  The principle of limited reduction in software design , 1990 .

[22]  Robert W. Zmud,et al.  A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques , 1992, MIS Q..

[23]  Paul Quintas,et al.  A product-process model of innovation in software development , 1994, J. Inf. Technol..

[24]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[25]  Jay F. Nunamaker,et al.  Information Technology to Support Electronic Meetings , 1988, MIS Q..

[26]  Jim Bryant Requirements capture using SODA , 1997 .

[27]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

[28]  W. Kickert Research Note: Research Models Underlying Situational Dependency , 1983 .

[29]  Robert L. Glass,et al.  Software tasks: Intellectual or clerical? , 1992, Inf. Manag..

[30]  Kalle Lyytinen,et al.  Different perspectives on information systems: problems and solutions , 1987, CSUR.

[31]  Arun Rai,et al.  The effects of development process modeling and task uncertainty on development quality performance , 2000, Inf. Manag..

[32]  Gail Salaway,et al.  An Organizational Learning Approach to Information Systems Development , 1987, MIS Q..

[33]  Robert P. Bostrom,et al.  MIS Problems and failures: a sociotechnical perspective part I: the cause , 1977 .

[34]  Gerald T. Mackulak,et al.  Stochastic simulation of risk factor potential effects for software development risk management , 2001, J. Syst. Softw..

[35]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

[36]  Iris Vessey,et al.  Requirements specification: learning object, process, and data methodologies , 1994, CACM.

[37]  Robert P. Bostrom,et al.  Successful application of communication techniques to improve the systems development process , 1989, Inf. Manag..

[38]  Moshe Telem,et al.  Information requirements specification I: Brainstorming collective decision-making approach , 1988, Inf. Process. Manag..

[39]  Enid Mumford,et al.  Review: Understanding and Evaluating Methodologies , 1995 .

[40]  Mark N. Frolick,et al.  EIS information requirements determination: Using a group support system to enhance the strategic business objectives method , 1995, Decis. Support Syst..

[41]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..

[42]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.

[43]  Sasa M. Dekleva,et al.  A note on the evolution of software engineering practices , 2001, J. Syst. Softw..

[44]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[45]  Sarma R. Nidumolu The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable , 1995, Inf. Syst. Res..

[46]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[47]  Brian Fitzgerald,et al.  Formalized systems development methodologies: a critical perspective , 1996, Inf. Syst. J..

[48]  Richard E. Zultner,et al.  TQM for technical teams , 1993, CACM.

[49]  L Candy,et al.  Knowledge-based system requirements , 1993, Knowl. Based Syst..

[50]  Richard Leifer,et al.  Deep structures: Real information requirements determination , 1994, Inf. Manag..

[51]  Leslie P. Willcocks,et al.  Risk assessment and information systems , 1993, ECIS.

[52]  Elizabeth J. Davidson,et al.  Technology Frames and Framing: A Socio-Cognitive Investigation of Requirements Determination , 2002, MIS Q..

[53]  Karen Holtzblatt,et al.  Requirements gathering: the human factor , 1995, CACM.

[54]  A. V. D. Ven,et al.  The Concept of Fit in Contingency Theory. , 1984 .

[55]  Alan M. Davis,et al.  Impacts of life cycle models on software configuration management , 1991, CACM.

[56]  Anthony R. Hendrickson,et al.  Research Commentary. Academic Rewards for Teaching, Research, and Service: Data and Discourse , 1999, Inf. Syst. Res..

[57]  F. W. McFarlan,et al.  Portfolio approach to information systems , 1989 .

[58]  Paul Grünbacher,et al.  System dynamics modelling and simulation of collaborative requirements engineering , 2001, J. Syst. Softw..

[59]  Justus D. Naumann,et al.  An experimental comparison of abstract and concrete representations in systems analysis , 1992, Inf. Manag..

[60]  Jan Stage,et al.  Prototyping and Specifying: Principles and Practices of a Mixed Approach , 1995, Scand. J. Inf. Syst..

[61]  Steve Sawyer,et al.  Software Development: Processes and Performance , 1998, IBM Syst. J..

[62]  Julio Cesar Sampaio do Prado Leite,et al.  Requirements Validation Through Viewpoint Resolution , 1991, IEEE Trans. Software Eng..

[63]  Nikolaos A. Mylonopoulos,et al.  On site: global perceptions of IS journals , 2001, CACM.

[64]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[65]  Evan W. Duggan Generating Systems Requirements With Facilitated Group Techniques , 2003, Hum. Comput. Interact..

[66]  M. Broadbent,et al.  Information and information technology management , 1988 .

[67]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..

[68]  Klaus Pohl,et al.  Requirements Elicitation and Validation with Real World Scenes , 1998, IEEE Trans. Software Eng..

[69]  Neil A. M. Maiden,et al.  Problem domain categories in requirements engineering , 1998, Int. J. Hum. Comput. Stud..

[70]  Glenn J. Browne,et al.  An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques , 2001, J. Manag. Inf. Syst..

[71]  Clyde W. Holsapple,et al.  Business Computing Research Journals: A Normalized Citation Analysis , 1994, J. Manag. Inf. Syst..

[72]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[73]  James C. Wetherbe Executive Information Requirements: Getting It Right , 1991, MIS Q..

[74]  Thiagarajan Ravichandran,et al.  Total Quality Management in Information Systems Development: Key Constructs and Relationships , 1999, J. Manag. Inf. Syst..

[75]  Suzanne Rivard,et al.  Toward an Assessment of Software Development Risk , 1993, J. Manag. Inf. Syst..

[76]  Jay F. Nunamaker,et al.  The architecture and design of a collaborative environment for systems definition , 1991, DATB.

[77]  Alan R. Hevner,et al.  Box-Structured Methods for Systems Development with Objects , 1993, IBM Syst. J..

[78]  Robert W. Zmud,et al.  Management of Large Software Development Efforts , 1980, MIS Q..

[79]  Sari Kujala,et al.  User involvement: A review of the benefits and challenges , 2003, Behav. Inf. Technol..

[80]  Bijan Fazlollahi,et al.  Selecting a requirement determination methodology-contingency approach revisited , 1991, Inf. Manag..

[81]  Colette Rolland,et al.  Guiding Lyee user requirements capture , 2003, Knowl. Based Syst..

[82]  Bill C. Hardgrave,et al.  Forums for management information systems scholars , 1995, CACM.

[83]  Mark L. Gillenson,et al.  Academic Issues in MIS: Journals and Books , 1991, MIS Q..

[84]  Bill Curtis,et al.  Process modeling , 1992, CACM.

[85]  Joseph S. Sherif,et al.  Object-oriented software design utilizing Quality Function Deployment , 1997, J. Syst. Softw..

[86]  Joyce J. Elam,et al.  Inside a software design team: knowledge acquisition, sharing, and integration , 1993, CACM.

[87]  Jay F. Nunamaker,et al.  Electronic meeting systems , 1991, CACM.

[88]  Tuure Tuunanen,et al.  Extending Critical Success Factors Methodology to Facilitate Broadly Participative Information Systems Planning , 2003, J. Manag. Inf. Syst..

[89]  J Ropponen,et al.  Can software risk management improve system development: an exploratory study , 1997 .

[90]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[91]  Jan Pries-Heje,et al.  How Internet software companies negotiate quality , 2001, Computer.

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

[93]  Rudy Hirschheim,et al.  Information Systems Development as Symbolism: Myth, Metaphor and Magic , 2002 .

[94]  Kalle Lyytinen,et al.  Attention Shaping and Software Risk - A Categorical Analysis of Four Classical Risk Management Approaches , 1998, Inf. Syst. Res..

[95]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[96]  K. Peffers,et al.  Identifying and Evaluating the Universe of Outlets for Information Systems Research: Ranking the Journals , 2003 .

[97]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[98]  Kishore Sengupta,et al.  Multimedia in a design rationale decision support system , 1995, Decis. Support Syst..

[99]  Hugh J. Watson,et al.  Determining Information Requirements for an EIS , 1993, MIS Q..

[100]  Carmen J. Trammell,et al.  Adopting Cleanroom Software Engineering with a Phased Approach , 1994, IBM Syst. J..

[101]  Alan R. Hevner,et al.  The incremental development process in Cleanroom software engineering , 1996, Decis. Support Syst..

[102]  Thiagarajan Ravichandran,et al.  Quality Management in Systems Development: An Organizational System Perspective , 2000, MIS Q..

[103]  Wen C. Pai,et al.  A Quality-Enhancing Software Function Deployment Model , 2002, Inf. Syst. Manag..

[104]  Barry W. Boehm,et al.  Theory-W Software Project Management: Principles and Examples , 1989, IEEE Trans. Software Eng..

[105]  Lars Mathiassen,et al.  Managing Risk in Software Process Improvement: An Action Research Approach , 2004, MIS Q..

[106]  Chetan S. Sankar,et al.  Reusability-Based Strategy for Development of Information Systems , 1990, MIS Q..

[107]  A. Jefferson Offutt,et al.  SOFL: A Formal Engineering Methodology for Industrial Applications , 1998, IEEE Trans. Software Eng..

[108]  Jonathan P. Bowen,et al.  Ten Commandments of Formal Methods , 1995, Computer.

[109]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[110]  Robert E. Kraut,et al.  Coordination in software development , 1995, CACM.

[111]  Woo Jin Lee,et al.  Integration and Analysis of Use Cases Using Modular Petri Nets in Requirements Engineering , 1998, IEEE Trans. Software Eng..