Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
skip to main content
article
Free access

An empirical validation of a contingency model for information require-ments determination

Published: 01 June 1998 Publication History
  • Get Citation Alerts
  • Abstract

    A contingency model for system development was subjected to several conceptual and operational adjustments and empirical tests. According to the model, there should be a degree of fit between development project uncertainty and the strategy for determining information requirements, ranging from accepting initial requirements statements to experimenting with prototypes to discover requirements. This study introduced a new IRD strategy construct that focused on the extent of interaction between users and developers. The study also differentiated between perceptual and evidential outcomes, between process and product outcomes, and between users' and developers' points of view. The hypotheses predicted that the degree of fit between project uncertainty and the IRD strategy would account for perceptual and evidential project outcomes from both the user's and developer's points of view. Results indicated that only by relying on the new extent of interaction construct, was support found. From the developers' standpoint, the degree of fit appeared to be related to perceptual assessments of the process and product. From the user's standpoint, the degree of fit was only related to perceptual assessments of the process. There was no support for the hypothesized impact of fit on evidential outcomes.

    References

    [1]
    Ackoff, R. L. (1967). "Management Misinformation Systems," Management Science, Vol. 14, No. 4, pp. 147-156.
    [2]
    Alavi, M. (1984). "An Assessment of the Prototyping Approach to Information Systems Development," Communications of the ACM, Vol. 27, No. 6, pp. 556-563.
    [3]
    Alter, S., and Ginzberg, M. (1978). "Managing Uncertainty in MIS Implementation," Sloan Management Review, pp. 23-31.
    [4]
    Baroudi, J. J. (1985). "The Impact of Role Variables on IS Personnel Work Attitudes and Intentions," MIS Quarterly, Vol. 9, No. 4, pp. 341-356.
    [5]
    Baroudi, J. J., and Ginzberg, M. J. (1986). "Impact of the Technological Environment on Programmer/ Analyst Job Outcomes," Communications of the ACM, Vol. 29, No. 6, pp. 546-555.
    [6]
    Beck, L. L., and Perkins, T. E. (1983). "A Survey of Software Engineering Practice: Tools, Methods and Results," IEEE Transactions on Software Engineering , SE-9, pp. 549-561.
    [7]
    Bellizzi, J. A., and Hite, R. E. (1986). "Face-to-Face Advance Contact and Monetary Incentives on Mail Survey Return Rates, Response Differences, and Survey Costs" Journal of Business Research, Vol. 14, No. 1, pp. 99-106.
    [8]
    Burns, R. N., and Dennis, A. R. (1985). "Selecting the Appropriate Application Development Methodology," Data Base, Vol. 17, No. 1, pp. 19-23.
    [9]
    Cohen, J., and Cohen, P. (1983). Applied Multiple Regression/Correlation Analysis for the Behavioral Sciences, NewHillsdale: Erlbaum.
    [10]
    Davis, G. B. (1982). "Strategies for Information Requirements Determination" IBM Systems Journal, Vol. 21, No. 1, pp. 4-30.
    [11]
    Davis, G. B., and Olson, M. H. (1985). Management Information Systems: Conceptual Foundations, Structure, and Development, New York: McGraw-Hill.
    [12]
    Dermer, J. D. (1973). "Cognitive Characteristics and the Perceived Importance of Information" The Accounting Review, Vol. 48, pp. 511-519.
    [13]
    Drazin, R., and Van de Ven, A. H. (1985). "Alternative Forms of Fit in Contingency Theory," Administrative Sciences Quarterly, Vol. 30, No. 4, pp. 514- 539.
    [14]
    El Louadi, M., Pollalis, Y. A., and Teng, J. T. C. (1991). "Selecting a Systems Development Methodology: A Contingency Framework" Information Resources Management Journal, Vol. 1, No. 1, pp. 11-19.
    [15]
    Elam, P. G. (1980). "Choosing Between System Development Alternatives," Journal of Systems Management , Vol. 31, No. 9, pp. 36-40.
    [16]
    Galbraith, J. (1977). Organization Design, Reading, PA: Addison-Wesley.
    [17]
    Galletta, D. E, and Heckman, R. L. (1990). "A Role Theory Perspective on End-user Development," Information Systems Research, Vol. 1, No. 2, pp. 168-187.
    [18]
    Ginzberg, M. J. (1978). "Redesign of Managerial Tasks: A Requisite for Successful Decision Support Systems" MIS Quarterly, Vol. 2, No. 1, pp. 39- 52.
    [19]
    Gorry, G. A., and Scott Morton, M. S. (1971 ). "A Framework for Management Information Systems," Sloan Management Review, Vol. 13, No. 1, pp. 55-70.
    [20]
    Green, G. I. (1989). "Perceived Importance of Systems 'Analysts' Job Skills, Roles, and Nonsalary Incentives" MIS Quarterly, Vol. 13, No. 2, pp. 115- 133.
    [21]
    Guinan, P. J. (1986). "Specialist-Generalist Communication Competence: An Investigation of the Communications Behavior of Information Systems Developers," Unpublished Doctoral Dissertation, Indiana University.
    [22]
    Guinan, P. J., and Bostrom, R. P. (1986). "Development of Computer-based Information Systems: A Communication Framework," Data Base, Vol. 17, No. 3, pp. 3-16.
    [23]
    Gremillion, L. L., and Pyburn, P. (1983), "Breaking the Systems Development Bottleneck," Harvard Business Review, Vol. 61, No. 2, pp. 130-137.
    [24]
    Hackathorn, R. D., and Karimi, J. (1988). "A Framework for Comparing Information Engineering Methods," MIS Quarterly, Vol. 12, No. 2, pp. 203-220.
    [25]
    Harel, E. C., and McLean, E. R. (1985). "The Effects of Using a Nonprocedural Language on Programmer Productivity," MIS Quarterly, Vol. 9, No. 2, pp. 109-120.
    [26]
    Ives, B., Olson, M. H., and Baroudi, J. J. (1983). "The Measurement of User-Information Satisfaction," Communications of the ACM, Vol. 26, No. 10, pp. 785-793.
    [27]
    Jenkins, A. M. (1985). "Prototyping: A Methodology for the Design and Development of Application Systems," Spectrum, Vol. 2, No. 2, pp. 1-8.
    [28]
    Jenkins, A. M., Naumann, J. D., and Wetherbe, J. C. (1984). "Empirical Investigation of Systems Development Practices and Results," Information & Management , Vol. 7., No. 2, pp. 73-82.
    [29]
    Kaiser, K. M., and King, W. R. (1982). "The Manager-Analyst Interface in Systems Development," MIS Quarterly, Vol. 6, No. 1, pp. 49-59.
    [30]
    King, W. R., and Cleland, D. I. (1971 ). "Manager-Analyst Teamwork in MIS: Cooperation Vital in Systems Design" Business Horizons, Vol. 14, No. 2, pp. 59-68.
    [31]
    Kurger, I., and Miller, J. R. (1976). "Management Information Systems-Success or Failure," Atlanta Economic Review, Vol. 2, pp. 6-10.
    [32]
    Leitheiser, R. L. (1992). "MIS Skills for the 1990s: A Survey of MIS Managers' Perceptions," Journal of MIS, Vol. 9, No. 1, pp. 69-91.
    [33]
    Lewyn, M. (April 26, 1993). "Flying in Place: The FAA's Air-Control Fiasco," Business Week, pp. 87-90.
    [34]
    Lucas, H. (1978). "Unsuccessful Implementation: The Case of a Computer-Based Order Entry System," Decision Sciences, Vol. 9, No. 2, pp. 68-79.
    [35]
    Lynch, D. (1984). "MIS: Conceptual Framework, Criticisms, and Major Requirements for Success," Journal of Business Communications, Vol. 22, pp. 1- 19.
    [36]
    Lyytinen, K. (1988). "Expectations Failure Concept and Systems Analysts View of Information Systems Failures: Results of an Exploratory Study," Information & Management, Vol. 14, pp. 45-56.
    [37]
    Martin, J. (1982). Application Development Without Programmers, Englewood Cliffs: Prentice Hall, Inc.
    [38]
    McFarlan, F. W. (1981). "Portfolio Approach to Information Systems," Harvard Business Review, Vol. 59, No. 5, pp. 142-150.
    [39]
    McKeen, J. D. (1983). "Successful Development Strategies for Business Application Systems," MIS Quarterly , Vol. 7, No. 3, pp. 47-65.
    [40]
    McKeen, J. D., Naumann, J. D., and Davis, G. B. (1979). "Development of a Selection Model for Information Requirements Determination," Working Paper Series MISRC-WP 79-06, University of Minnesota, 1979, pp. 1-14.
    [41]
    McLean, E. (1979). "End Users as Application Developers," MIS Quarterly, Vol. 3, No. 4, pp. 37-46.
    [42]
    Moore, J. H., and Chang, M. G. (1980). "Design of DSS," Data Base, Vol. 12, No. 1-2, 1980, pp. 8-14.
    [43]
    Munro, M. C. (1978). "Determining the Manager's Information Needs," Journal of Systems Management , Vol. 29, No. 6, pp. 34-39.
    [44]
    Munro. M. C., and Davis, G. B. (1977). "Determining Management Information Needs: A Comparison of Methods," MIS Quarterly, Vol. 1, No. 2, pp. 55-67.
    [45]
    Naumann, J. D., and Davis, G. B. (1978). "Contingency Theory Approach to Systems Life Cycle Management," Proceedings of the Second Software Life Cycle Management Work, pp. 63-65.
    [46]
    Naumann, J. D., Davis, G. B., and McKeen, J. D. (1980). "Determining Information Requirements: A Contingency Method for Selection of a Requirements Assurance Strategy," The Journal of Systems and Software, Vol. 1, No. 4, pp. 273-281.
    [47]
    Naumann, J. D., and Jenkins, A. M. (1982). "Prototyping: The New Paradigm for Systems Development," MIS Quarterly, Vol. 6, No. 3, pp. 29-44.
    [48]
    Naumann, J. D., Jenkins, A. M., and Wetherbe, J. C. (1983). "The Information Requirements Determination Contingency Model: An Empirical Investigation," Unpublished Manuscript, pp. 1-35.
    [49]
    Palvia, P., and Nosek, J. (1993)., "A Field Examination of System Life Cycle Techniques and Methodologies," Information & Management, Vol. 25, pp. 73-84.
    [50]
    Powers, R. F. (1971). "An Empirical Investigation of Selected Hypotheses Related to the Success of Management Information System Project," Unpublished Ph.D. Dissertation, University of Minnesota.
    [51]
    Ross, D. T., and Schoman, K. E. (1977). "Structured Analysis for Requirements Definition," IEEE Transactions on Software Engineering, SE-3, No. 1, pp. 6-15.
    [52]
    Saarinen, T. (1990). "System Development Methodology and Project Success: An Assessment of Situational Approaches," Information & Management, Vol. 19, pp. 183-193.
    [53]
    Schmitt, J. W., and Kozar, K. A. (1978). "Management's Role in Information System Development Failures: A Case Study," MIS Quarterly, Vol. 2, No. 2, pp. 7-16.
    [54]
    Soden, J. V. (1975). "Understanding MIS Failures," Data Management, Vol. 13, pp. 7-29.
    [55]
    Taggart, W. M., and Tharp, M. O. (1977), "A Survey of Information Requirements Analysis Techniques," Computing Surveys, Vol. 9, No. 4, pp. 273-290.
    [56]
    Teng, J. T. C., and Galletta, D. E. (1990). "MIS Research Directions: A Survey of Researchers' Views," Data Base, Vol. 21, No. 2&3, pp. 1-10.
    [57]
    Venkatraman, N., and Camillus, J. C. (1984). "Exploring the Concept of 'Fit'," Academy of Management Review, Vol. 3, No. 3, pp. 513-525.
    [58]
    Venkatraman, N. (1989). "The Concept of Fit in Strategy Research: Toward Verbal and Statistical Correspondence," Academy of Management Review, Vol. 14, No. 3, pp. 423-444.
    [59]
    Wrigley, C., and Dexter, A. S. (1991). "A Model for Measuring Information System Size," MIS Quarterly , Vol. 15, No. 2, pp. 245-264.
    [60]
    Zellner, W. (January 17, 1994). "Portrait of a Project as a Total Disaster," Business Week, Vol. 36.

    Cited By

    View all
    • (2003)A three‐stage model of requirements elicitation for Web‐based information systemsIndustrial Management & Data Systems10.1108/02635570310479972103:6(398-409)Online publication date: Aug-2003
    • (2001)A systems view of the evolution in information systems developmentSystems Research and Behavioral Science10.1002/sres.44119:1(61-75)Online publication date: 12-Dec-2001

    Recommendations

    Comments

    Information & Contributors

    Information

    Published In

    cover image ACM SIGMIS Database: the DATABASE for Advances in Information Systems
    ACM SIGMIS Database: the DATABASE for Advances in Information Systems  Volume 29, Issue 3
    Summer 1998
    79 pages
    ISSN:0095-0033
    EISSN:1532-0936
    DOI:10.1145/313310
    Issue’s Table of Contents

    Publisher

    Association for Computing Machinery

    New York, NY, United States

    Publication History

    Published: 01 June 1998
    Published in SIGMIS Volume 29, Issue 3

    Check for updates

    Author Tags

    1. contingency model
    2. fit model
    3. information requirements determination
    4. systems development

    Qualifiers

    • Article

    Contributors

    Other Metrics

    Bibliometrics & Citations

    Bibliometrics

    Article Metrics

    • Downloads (Last 12 months)29
    • Downloads (Last 6 weeks)2

    Other Metrics

    Citations

    Cited By

    View all
    • (2003)A three‐stage model of requirements elicitation for Web‐based information systemsIndustrial Management & Data Systems10.1108/02635570310479972103:6(398-409)Online publication date: Aug-2003
    • (2001)A systems view of the evolution in information systems developmentSystems Research and Behavioral Science10.1002/sres.44119:1(61-75)Online publication date: 12-Dec-2001

    View Options

    View options

    PDF

    View or Download as a PDF file.

    PDF

    eReader

    View online with eReader.

    eReader

    Get Access

    Login options

    Media

    Figures

    Other

    Tables

    Share

    Share

    Share this Publication link

    Share on social media