Improving information requirements determination: a cognitive perspective

Requirements determination is a critical phase of information systems development, but much evidence suggests that the process can and should be improved. Because the bulk of requirements determination occurs early in the development of a system, improvements can yield significant benefits for the entire systems development process. This paper first discusses a three-stage descriptive model of the requirements determination process. Four classes of difficulties in determining systems requirements are then used to organize and describe particular problems that occur within each stage of the process, together with the cognitive and behavioral theories that underlie them. The paper then describes techniques that can address the problems and presents theoretical considerations that analysts can use in applying the techniques to improve requirements determination.

[1]  I. Janis.  Victims Of Groupthink , 1972 .

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

[3]  Michael Ross,et al.  The remembering self Construction and accuracy in the self-narrative: Creative remembering , 1994 .

[4]  Lívia Markíczy,et al.  A Method for Eliciting and Comparing Causal Maps , 1995 .

[5]  J. F. Courtney,et al.  A system for organizational learning using cognitive maps , 1992 .

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

[7]  Glenn J. Browne,et al.  Evoking Information in Probability Assessment: Knowledge Maps and Reasoning-Based Directed Questions , 1997 .

[8]  Robert W. Zmud,et al.  The use of mental imagery as a requirements analysis technique , 1992 .

[9]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[10]  H. McIlvaine Parsons,et al.  Hawthorne:: An Early OBM Experiment , 1991 .

[11]  Kuldeep Kumar,et al.  Strategies for incorporating formal specifications in software development , 1994, CACM.

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

[13]  Harry Nyström,et al.  Creativity and Innovation , 1979 .

[14]  Vinod Goel,et al.  Motivating the Notion of Generic Design within Information-Processing Theory: The Design Problem Space , 1989, AI Mag..

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

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

[17]  H. Simon,et al.  Information Processing Models of Cognition , 1979 .

[18]  W. Brewer.  Remembering reconsidered: Memory for randomly sampled autobiographical events , 1988 .

[19]  A. Tversky,et al.  Judgment under Uncertainty: Heuristics and Biases , 1974, Science.

[20]  P. Barnard,et al.  How would your favourite user model cope with these scenarios? , 1989, SGCH.

[21]  Karim Jamal,et al.  Effects of framing on auditor decisions , 1990 .

[22]  Paul H. Cheney,et al.  A Theoretically Grounded Approach to Assist Memory Recall During Information Requirements Determination , 1998, J. Manag. Inf. Syst..

[23]  Carl-Axel S. Staël von Holstein,et al.  Exceptional Paper---Probability Encoding in Decision Analysis , 1975 .

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

[25]  Donald J. Reifer,et al.  Web Development: Estimating Quick-to-Market Software , 2000, IEEE Softw..

[26]  Janice Redish,et al.  User and task analysis for interface design , 1998 .

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

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

[29]  Chris Gane,et al.  Structured Systems Analysis: Tools and Techniques , 1977 .

[30]  J. D. Couger,et al.  Creativity/Innovation in Information Systems Organizations Introduction to Session , 1996, Proceedings of HICSS-29: 29th Hawaii International Conference on System Sciences.

[31]  Ronald A. Howard,et al.  Knowledge Maps , 1989 .

[32]  J. D. Couger,et al.  Creativity/Innovation in Information Systems Organizations , 1995, Proceedings of the Thirtieth Hawaii International Conference on System Sciences.

[33]  Daniel Kahneman,et al.  Availability: A heuristic for judging frequency and probability , 1973 .

[34]  Herbert A. Simon,et al.  The Sciences of the Artificial , 1970 .

[35]  A. Tversky,et al.  On the psychology of prediction , 1973 .

[36]  John M. Carroll,et al.  Scenario-based design: envisioning work and technology in system development: john wiley & sons , 1995 .

[37]  R. Wood.  Task complexity: Definition of the construct , 1986 .

[38]  Kee-Young Kwahk,et al.  Supporting business process redesign using cognitive maps , 1999, Decis. Support Syst..

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

[40]  Surya B. Yadav,et al.  The Design of a Knowledge-Based Decision Support System to Support the Information Analyst in Determining Requirements , 1992 .

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

[42]  Glenn J. Browne,et al.  Arguments in the practical reasoning underlying constructed probability responses , 1995 .

[43]  Mary Lippitt Nichols,et al.  AN INVESTIGATION OF MOTIVATIONAL BIAS IN SUBJECTIVE PREDICTIVE PROBABILITY DISTRIBUTIONS , 1982 .

[44]  H. Joel Jeffrey,et al.  Relationship definition and management: Tools for requirements analysis , 1994, J. Syst. Softw..

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

[46]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

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

[48]  Webb Stacy,et al.  Cognitive bias in software engineering , 1995, CACM.

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

[50]  Veda C. Storey,et al.  Understanding Database Design Expertise , 1995, Data Knowl. Eng..

[51]  T. M. Rajkumar,et al.  Comparison of analysis techniques for information requirement determination , 1988, CACM.

[52]  Lynn Hasher,et al.  Is memory schematic , 1983 .

[53]  B. Fischhoff,et al.  Judgment under uncertainty: Debiasing , 1982 .

[54]  A. Nico Habermann,et al.  Software Development Environments , 1987, Computer.

[55]  Gerald F. Smith,et al.  Belief assessment: an underdeveloped phase of probability elicitation , 1995 .

[56]  H. Simon,et al.  Models of Man. , 1957 .

[57]  Baruch Fischhoff,et al.  Focusing Techniques: A Shortcut to Improving Probability Judgments? , 1984 .

[58]  J. Baron,et al.  Heuristics and biases in diagnostic reasoning: II. Congruence, information, and certainty☆ , 1988 .

[59]  M. Gluck,et al.  Explaining Basic Categories: Feature Predictability and Information , 1992 .

[60]  Jon A. Turner.  A Comparison of the Process of Knowledge Elicitation with that of Information Requirements Determination , 1990 .

[61]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

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

[63]  M. Brassard.  The Memory Jogger Plus , 1991 .

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

[65]  Peter G. W. Keen,et al.  Information systems and organizational change , 1990, CACM.

[66]  J. Baron,et al.  An analysis of the word-superiority effect☆ , 1973 .

[67]  V. Reyna,et al.  Explaining “Memory Free” Reasoning 1 , 1992 .

[68]  Nicholas P. Vitalari,et al.  Structuring the requirements analysis process for information systems: a proposition viewpoint , 1992 .

[69]  Nicholas P. Vitalari,et al.  Differences Between Novice and Expert Systems Analysts: What Do We Know and What Do We Do? , 1998, J. Manag. Inf. Syst..

[70]  M. Bazerman.  Judgment in Managerial Decision Making , 1990 .

[71]  Leslie Johnson,et al.  Knowledge Elicitation Involving Teachback Interviewing , 1987 .

[72]  Kuldeep Kumar,et al.  Informal and Formal Requirements Specification Languages: Bridging the Gap , 1991, IEEE Trans. Software Eng..

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

[74]  B. Fischhoff,et al.  Reasons for confidence. , 1980 .

[75]  Arkalgud Ramaprasad,et al.  A computerized interactive technique for mapping influence diagrams (MIND) , 1985 .

[76]  G. Waters,et al.  Processing resource capacity and the comprehension of garden path sentences , 1996, Memory & cognition.

[77]  Angela M. O'Donnell.  Searching for Information in Knowledge Maps and Texts , 1993 .

[78]  Glenn J. Browne,et al.  Representing User Requirements:An Empirical Investigation of Formality in Modeling Tools , 1997 .

[79]  Surya B. Yadav,et al.  Determining an organization's information requirements: a state of the art survey , 1983, DATB.

[80]  Richard J. Boland,et al.  Sense-Making of Accounting Data as a Technique of Organizational Diagnosis , 1984 .

[81]  C. Randall Byers,et al.  Tying critical success factors to systems development , 1994, Inf. Manag..

[82]  Russell L. Ackoff,et al.  Management misinformation systems , 1967 .

[83]  Robert F. Dell,et al.  Optimizing Plant-Line Schedules and an Application at Hidden Valley Manufacturing Company , 2002, Interfaces.

[84]  W. Edwards,et al.  Decision Analysis and Behavioral Research , 1986 .