A user-oriented model of factors that affect information requirements determination process quality

Information Resources Management Journal

Volumn 16, Issue 4, 2003, Pages 15-32

  Havelka, Douglas ^a  

^a MIAMI UNIVERSITY   (United States)

Author keywords

End user; Information requirements determination; Process quality; Requirements engineering; Software development

Indexed keywords

COMPUTER SOFTWARE; INFORMATION DISSEMINATION; INFORMATION TECHNOLOGY; INTERACTIVE COMPUTER SYSTEMS; METRIC SYSTEM; PROJECT MANAGEMENT; QUALITY OF SERVICE; REQUIREMENTS ENGINEERING; SOFTWARE ENGINEERING;

PROCESS QUALITY;

INFORMATION MANAGEMENT;

EID: 0042379670     PISSN: 10401628     EISSN: None     Source Type: Journal    
DOI: 10.4018/irmj.2003100102     Document Type: Article

References (94)

1. Adam, E. E. J., Hershauer, J., & Ruch, W. (1986). Productivity and quality Management as a Basis for Improvement. Columbia, MO: University of Missouri, College of Business Research Center.
2. Adolph, S. (2000). Lost in chaos: Chronology of a failure. Software Development Magazine Online.
3. Agarwal, R., Sinha, A. P., & Tanniru, M. (1996). Cognitive fit in requirements modeling: A study of object and process methodologies. Journal of Management Information Systems, 13(2), 137-162.
4. Atkinson, C. J. (2000). Socio-technical and soft approaches to information requirements elicitation in the post-methodology era. Requirements Engineering, 5(2), 67-73.
5. Barki, H., & Hartwick, J. (1994a). Measuring user participation, user involvement, and user attitude. MIS Quarterly, 18(1), 59-82.
6. Barki, H., & Hartwick, J. (1994b). User participation, conflict, and conflict resolution: The mediating roles of influence. Information Systems Research, 5(4), 422-438.
7. Bergeron, F., & Begin, C. (1989). The use of critical success factors in evaluation of information systems: A case study. Journal of Management Information Systems, 5(4), 111-124.
8. Bergey, J., Smith, D., Tilley, S., Weiderman, N., & Woods, S. (1999). Why Reengineering Projects Fail (Technical Report CMU/SEI-99-TR-010). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon.
9. Berry, D. M. (1995). The importance of ignorance in requirements engineering. Journal of Systems & Software, 28, 179-184.
10. Berry, D. M. (1998). Software and house requirements engineering: Lessons learned in combating requirements creep. Requirements Engineering, 3(3/4), 242-244.
11. Berry, D. M. (2002). The importance of ignorance in requirements engineering: An earlier sighting and a revisitation. Journal of Systems and Software, 60, 83-85.
12. Bostrom, R. P. (1989). Successful application of communication techniques to improve the systems development process. Information and Management, 16, 279-295.
13. Browne, G. J., & Rogich, M. B. (2001). An empirical investigation of user requirements elicitation: Comparing the effectiveness of prompting techniques. Journal of Management Information Systems, 17(4), 223-240.
14. Byrd, T. A., Cossick, K.L., and Zmud, R.W. (1992). A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Quarterly, 16(1), 117-138.
15. Chatzoglou, P. D. (1997). Factors affecting completion of the requirements capture stage of projects with different characteristics. Information & Software Technology, 39, 627-640.
16. Chatzoglou, P. D., & Macaulay, L. A. (1996). Requirements capture and IS methodologies. Information Systems Journal, 5(3), 209-225.
17. Chatzoglou, P. D., & Soteriou, A. C. (1999). A DBA framework to assess the efficiency of the software requirements capture and analysis process. Decision Sciences, 30(2), 503.
18. Choe, J. (1998). The effects of user participation on the design of accounting information systems. Information & Management, 34(3), 185-198.
19. Colter, M. A. (1984). A comparative analysis of systems analysis techniques. MIS Quarterly, 5(1), 51-66.
20. Conover, W. J. (1980). Practical Nonparametric Statistics (2nd ed). New York: John Wiley & Sons.
21. Coughlan, J., & Macredie, R. D. (2002). Effective communication in requirements elicitation: A comparison of methodologies. Requirements Engineering, 7(2), 47-60.
22. Cronan, T. P., & Means, T. L. (1984). System development: An empirical study of user communication. Data Base, 25-33.
23. Cysneiros, L. M., Leite, J. C., & Neto, J. (2001 ). A framework for integrating non-functional requirements into conceptual models. Requirements Engineering, 6(2), 97-115.
24. Daugulis, A. (2000). Time aspects in requirements engineering: Or 'every cloud has a silver lining.' Requirements Engineering, 5(3), 137-143.
25. Davis, G. B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21(1), 4-30.
26. DeBrabander, B., & Thiers, G. (1984). Successful information system development in relation to situational factors which affect effective communication between MIS-Users and EDP-Specialists. Management Science, 30(2), 137-155.
27. Delbecq, A. L., Van De Ven, A. H., & Gustafson, D. H. (1982). Guidelines for conducting NGT meetings. In Hampton, D. R., Summer, C. E. & Webber, R. A. (Eds.), Organizational Behavior and the Practice of Management. (4th ed., pp. 279-298). Glenview, IL: Scott, Foresman, and Company.
28. Doll, W. J., & Torkzadeh, G. (1989). A discrepancy model of end-user computing involvement. Management Science, 35(10), 1151-1171.
29. Doll, W. J., & Torkzadeh, G. (1991). A congruence construct of user involvement. Decision Sciences, 22(2), 443-453.
30. Frame, J. D. (1995). Managing Projects in Organizations (revised ed.). San Francisco, CA: Jossey-Bass Publishers.
31. Galal, G. H., & Paul, R. J. (1999). A qualitative scenario approach to managing evolving requirements. Requirements Engineering, 4(2), 92-102.
32. Glass, R. L. (2000). Software requirements success predictors - behavioral factors beat technical ones. Journal of Systems and Software, 51, 85-86.
33. Grudnitski, G. (1984). Eliciting decision-makers' information requirements: Application of the Rep Test methodology. Journal of Management Information Systems, 1(1), 11-32.
34. Guinan, P., Cooprider, J., & Faraj, S. (1998). Enabling software development team performance during requirements definition: A behavioral versus technical approach. Information Systems Research, 9(2), 101-125.
35. Gunter, C. A., Gunter, E. L., & Jackson, M. (2000). A reference model for requirements and specifications. IEEE Software, 77(3), 37-43.
36. Havelka, D. (2002). Requirements determination: An information systems specialist perspective of process quality. Requirements Engineering, 6(4), 220-236.
37. Havelka, D., Sutton, S. G., & Arnold, V. (1998). A methodology for developing measurement criteria for assurance services: An application in information systems assurance. Auditing: A Journal of Practice & Theory, 17(Supplement), 73-92.
38. Havelka, D., Sutton, S. G., & Arnold, V. (2001). Information systems quality assurance: The effect of users' experiences on quality factor perceptions. Review of Business Information Systems, 5(2), 49-62.
39. Hevner, A. R., & Harlan, D. M. (1995). Box-structured requirements determination methods. Decision Support Systems, 13, 223-239.
40. Holtzblatt, K., & Beyer, H. R. (1995). Requirements gathering: The human factor. Communications of the ACM, 38(5), 30-32.
41. Hunton, J. E. (1996a). Involving information system users in defining system requirements: The influence of procedural justice perceptions on user attitudes and performance. Decision Sciences, 27(4), 647-671.
42. Hunton, J. E. (1996b). User participation in defining system interfact requirements: An issue of procedural justice. Journal of Information Systems, 10(1), 27-48.
43. Ives, B., & Olson, M. (1984). User involvement and MIS success: A review of research. Management Science, 30(5), 586-603.
44. Janson, M., Brown, A., & Taillieu, T. (1997). Colruyt: An organization committed to communication. Information Systems Journal, 7(3), 175-199.
45. Janson, M. A., & Woo, C. C. (1996). A speech act lexicon: An alternative use of speech act theory in information systems. Information Systems Journal, 6(4), 301-329.
46. Johnson, J. (1995). Chaos: The dollar drain of IT project failures. Application Development Trends, 2(1), 47-47.
47. Kaiser, K. M., & King, W. R. (1982). The manager-analyst interface in systems development. MIS Quarterly, 49-59.
48. Kaiser, K. M., & Srinivasan, A. (1982). User-analyst differences: An empirical investigation of attitudes related to systems development. Academy of Management Journal, 25(3), 630-646.
49. Kiel, M., & Carmel, E. (1995). Customer-developer links in software development. Communications of the ACM, 38(5).
50. Lauesen, S., & Vinter, O. (2001). Preventing requirement defects: An experiment in process improvement. Requirements Engineering, 6(1), 37-50.
51. Leifer, R., Lee, S., & Durgee, J. (1994). Deep structures: Real information requirements determination. Information & Management, 27(5), 275-285.
52. Lockwood, D. L. (1989). Using facilitated team techniques to define information systems requirements. Journal of IS Education, 2(1).
53. Macaulay, L. A. (1999). Seven-layer model of the role of the facilitator in requirements engineering. Requirements Engineering, 4(1), 38-59.
54. Mantha, R. W. (1987). Data flow and data structure modeling for database requirements cetermination: A comparative study. MIS Quarterly, 531-545.
55. Marakas, G., & Elam, J. (1998). Semantic structuring in analyst acquisition and representation of facts in requirements analysis. Information Systems Research, 9(1), 37-63.
56. Markus, M. L. (1981). Implementation politics: Top management support and user involvement. Information and Management, 1, 203-215.
57. Markus, M. L. (1983). Power, politics, and MIS implementation. Communications of the ACM, 26, 430-444.
58. McKeen, J. D., & Guimaraes, T. (1997). Successful strategies for user participation in systems development. MIS Quarterly, 14(2), 133-150.
59. Montezemi, A. R., & Conrath, D. W. (1986). The use of cognitive mapping for information requirement analysis. MIS Quarterly, 10(1), 45-56.
60. Moody, J. W., Blanton, J. E., & Cheney, P. H. (1998). A theoretically grounded approach to assist memory recall during information requirements determination. Journal of Management Information Systems, 15(1), 79-98.
61. Newman, M., & Noble, F. (1990). User involvement as an interaction process: A case study. Information Systems Research, 1(1), 89-113.
62. Ocker, R., Fjermestad, J., Hiltz, S. R., & Johnson, K. (1998). Effects of four modes of group communication on the outcomes of software requirements determination. Journal of Management Information Systems, 15(1), 99-118.
63. Ocker, R., & Hiltz, S. R. (1995/96). The effects of distributed group support and process structuring on software requirements. Journal of Management Information Systems, 12(3), 127-154.
64. Patel, N. V. (1999). The spiral of change model for coping with changing and ongiong requirements. Requirements Engineering, 4(2), 77-84.
65. Paul, R. J., & Macredie, R. D. (1999). Guest editorial: Managing dynamic requirements. Requirements Engineering, 4(2), 63-64.
66. Rademacher, R. A. (1989). Critical success factors for systems success. Journal of Systems Management, 15-17.
67. Regnell, B., Host, M., Dag, J. N., Beremark, P., & Hjelm, T. (2001). An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software. Requirements Engineering, 6(1), 51-62.
68. Robey, D. (1984). Conflict models for implementation research. Applications of Management Science, Supplement 1 (89-105): JAI Press.
69. Robey, D. (1994). Modeling Interpersonal processes during system development: Further thoughts and suggestions. Information Systems Research, 5(4), 439-445.
70. Robey, D., Farrow, D. L., & Franz, C. R. (1989). Group process and conflict in system development. Management Science, 35(10), 1172-1191.
71. Robey, D., Farrow, D.L., and Franz, C. R. (1986). Group process and conflict in system development. Management Science, 35(10), 1172-1191.
72. Robey, D., Smith, L., & Vijaysarathy, L. (1993). Perceptions of conflict and success in information systems development projects. Journal of Management Information Systems, 10(1), 123-139.
73. Robey, D., (1982). User involvement in information system development: A conflict model and empirical test. Management Science, 28(1), 73-85.
74. Robey, D. S., L.A., and Vijayasarathy, L.R. (1993). Perceptions of conflict and success in information systems development projects. Journal of Management Information Systems, 10(1), 123-140.
75. Schmidt, R., Lyytinen, K., Keil, M., & Cule, P. (2001). Identifying software project risks: An international Delphi study. Journal of Management Information Systems, 17(4), 5-36.
76. Sibley, E. H., & Bailin, S. C. (1989). An object-oriented requirements specification method. Communications of the ACM, 32(5), 608-624.
77. Soffer, P., Golany, B., Dori, D., & Wand, Y. (2001). Modelling off-the-shelf systems requirements: An ontological approach. Requirements Engineering, 6(3), 183-199.
78. Sutcliffe, A. G. (2000). Requirements analysis for socio-technical system design. Information Systems, 25(3), 213-233.
79. Sutton, S. G. (1993). Toward an understanding of the factors affecting audit quality. Decision Sciences, 88-105.
80. Taggart, W. M., Jr. & Tharp, M.O. (1977). A survey of information requirements analysis techniques. Computing Surveys, 9(4), 273-290.
81. Torkzadeh, G., & Doll, W. J. (1991). Test-retest reliability of end-user computing satisfaction instrument. Decision Sciences, 22(1), 26-37.
82. Torkzadeh, G., & Doll, W. J. (1994). The test-retest reliability of user involvement instruments. Information & Management, 26(1), 21-31.
83. Van De Yen, A. H., & Delbecq, A. L. (1974). The effectiveness of nominal, Delphi, and interacting group decision making processes. Academy of Management Journal, 17(4), 605-621.
84. Vessey, I., & Conger, S. (1993). Learning to specify information requirements: The relationship between application and methodology. Journal of Management Information Systems, 10(2), 177-201.
85. Vessey, I., & Conger, S. (1994). Requirements specification: Learning object, process, and data methodologies. Communications of the ACM, 37(5), 102-114.
86. Viller, S., Bowers, J., & Rodden, T. (1999). Human factors in requirements engineering: A survey of human sciences literature relevant to the improvement of dependable systems development processes. Interacting with Computers, 11(6), 665-698.
87. Watson, H., & Frolick, M. (1993). Determining information requirements for an EIS. MIS Quarterly, 17(3), 255-270.
88. Webb, L. A. (2000). Information Requirements Determination for Electronic Retailing: A Consumer-Based Perspective. Paper presented at the Americas Conference on Information Systems, Long Beach, CA. (August 10-13).
89. Wetherbe, J. C. (1991). Executive information requirements: Getting it right. MIS Quarterly, 15(1), 51-65.
90. Woodroof, J. B. (1996). Discussion of user participation in defining system interface requirements: An issue of procedural justice. Journal of Information Systems, 10(1), 49-51.
91. Yadav, S. B. (1983). Determining an organization's information requirements: A state-of-the-art survey. Data Base, 14(3), 3-20.
92. Yadav, S. B. (1985). Classifying an organization to identify its information requirements: A comprehensive framework. Journal of Management Information Systems, 2(1), 39-59.
93. Yadav, S. B., Bravoco, R. R., Chatfield, A. T., & Rajkumar, T. M. (1988). Comparison of analysis techniques for information requirement determination. Communications of the ACM, 31(9), 1090-1098.
94. Zmud, R. W., Anthony, W. P., & Stair, R. M. J. (1993). The use of mental imagery to facilitate information identification in requirements analysis. Journal of Management Information Systems, 9(4), 175-192.