Strategies for Information Requirements Determination

Correct and complete information requirements are key ingredients in planning organizational information systems and in implementing information systems applications. Yet, there has been relatively little research on information requirements determination, and there are relatively few practical, well-formulated procedures for obtaining complete, correct information requirements. Methods for obtaining and documenting information requirements are proposed, but they tend to be presented as general solutions rather than alternative methods for implementing a chosen strategy of requirements determination. This paper identifies two major levels of requirements: the organizational information requirements reflected in a planned portfolio of applications and the detailed information requirements to be implemented in a specific application. The constraints on humans as information processors are described in order to explain why "asking" users for information requirements may not yield a complete, correct set. Various strategies for obtaining information requirements are explained. Examples are given of methods that fit each strategy. A contingency approach is then presented for selecting an information requirements determination strategy. The contingency approach is explained both for defining organizational information requirements and for defining specific, detailed requirements in the development of an application.

[1]  Richard L. Nolan,et al.  What Kind of Corporate Modeling Functions Best , 1974 .

[2]  James C. Wetherbe,et al.  Heuristic Development: A Redesign of Systems Design , 1979, MIS Q..

[3]  Göran Goldkuhl,et al.  Information Systems Development: A Systematic Approach , 1981 .

[4]  Hugh J. Lynch,et al.  ADS: a technique in systems documentation , 1969, DATB.

[5]  Ben Shneiderman,et al.  Software psychology: Human factors in computer and information systems (Winthrop computer systems series) , 1980 .

[6]  James C. Miller Conceptual models for determining information requirements , 1964, AFIPS '64 (Spring).

[7]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[8]  Gordon B. Davis,et al.  Determining information requirements: A contingency method for selection of a requirements assurance strategy , 1984, J. Syst. Softw..

[9]  William R. King,et al.  Strategic Planning for Management Information Systems , 1978, MIS Q..

[10]  A. Milton Jenkins,et al.  What the information analyst should know about body language , 1977 .

[11]  George P. Huber,et al.  The People Side of Systems. , 1977 .

[12]  Allen Newell,et al.  Human Problem Solving. , 1973 .

[13]  Robert P. Bostrom,et al.  Mis problems and failures: a socio-technical perspective , 1977 .

[14]  Nicholas Paul Vitalari,et al.  An investigation of the problem solving behavior of systems analysts , 1981 .

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

[16]  William R. King,et al.  The Design of Management Information Systems an Information Analysis Approach , 1975 .

[17]  Tom DeMarco,et al.  Structured Analysis and System Specification , 1978 .

[18]  Walter M. Carlson,et al.  Business information analysis and integration technique (BIAIT): the new horizon , 1979, DATB.

[19]  J. Daniel Couger,et al.  Evolution of Business System Analysis Techniques , 1973, CSUR.

[20]  G. A. Miller THE PSYCHOLOGICAL REVIEW THE MAGICAL NUMBER SEVEN, PLUS OR MINUS TWO: SOME LIMITS ON OUR CAPACITY FOR PROCESSING INFORMATION 1 , 1956 .

[21]  Gordon B. Davis,et al.  Determining Management Information Needs: A Comparison of Methods , 1977, MIS Q..

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