The Effect of Task and Tool Experience on Maintenance Case Tool Usage

Information Resources Management Journal

Volumn 16, Issue 3, 2003, Pages 1-16

  Dishaw, Mark T ^b   Strong, Diane M ^a  

^a WORCESTER POLYTECHNIC INSTITUTE   (United States)

^b NONE

Author keywords

Baseline Maintenance Tool Utilization ModelComputer Aided Software Engineering (CASE); Maintenance Tool Utilization Model

Indexed keywords

COMPUTER PROGRAMMING; COMPUTER SOFTWARE MAINTENANCE;

SOFTWARE MAINTENANCE SUPPORT TOOLS;

COMPUTER AIDED SOFTWARE ENGINEERING;

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

References (40)

1. Arunachalam, V., & Sasso, W. (1996). Cognitive processes in program comprehension: An empirical analysis in the context of software reengineering. Journal of Systems and Software, 34(3), 177-189.
2. Cohen, J., & Cohen, P. (1983). Applied Multiple Regression/Correlation Analysis for the Behavioral Sciences. (2nd ed.). Hillsdale, NJ: Lawrence Erlbaum Associates.
3. Davis, F. D., Jr. (1985). A Technology Acceptance Model for Empirically Testing New End-User Systems: Theory and Results. Unpublished PhD, Massachusetts Institute of Technology.
4. Davis, F. D., Bagozzi, R. P., & Warshaw, P. R. (1989). User acceptance of computer technology: A comparison of two theoretical models. Management Science, 35(8), 982-1003.
5. Dishaw, M. T., & Strong, D. M. (1998a). Assessing software maintenance tool utilization using task-technology fit and fitness-for-use models. Journal of Software Maintenance: Research and Practice, 10(3), 151-179.
6. Dishaw, M. T., & Strong, D. M. (1998b). Supporting software maintenance with software engineering tools: A computed task-technology fit analysis. Journal of Systems and Software, 44, 107-120.
7. Dishaw, M. T., & Strong, D. M. (1999). Extending the technology acceptance model with task-technology fit constructs. Information and Management, 36(1), 9-21.
8. Goodhue, D. L. (1988). I/S attitudes: Toward theoretical and definitional clarity. Data Base, 19(3/4), 6-15.
9. Goodhue, D. L. (1992). User Evaluations of MIS Success: What Are We Really Measuring? Paper presented at the Hawaii International Conference on System Sciences, Kona, Hawaii.
10. Goodhue, D. L. (1995). Understanding user evaluations of information systems. Management Science, 41(12), 1827-1844.
11. Goodhue, D. L., & Thompson, R. L. (1995). Task-technology fit and individual performance. MIS Quarterly, 19(2), 213-236.
12. Griswold, W. G., & Atkinson, D. C. (1995). Managing design trade-offs for a program understanding and transformation tool. Journal of Systems and Software, 30(1-2), 99-116.
13. Guinan, P. J., Cooprider, J. G., & Sawyer, S. (1997). The effective use of automated application development tools. IBM Systems Journal, 36(1), 124-139.
14. Guinan, P. J., Hopkins, G. N., & Cooprider, J. G. (1992). Automation of the Applications Development Life Cycle: Measuring the Value Added. Paper presented at the International Conference on Information Systems, Dallas, Texas.
15. Gupta, A. K., & Govindarajan, V. (1984). Business unit strategy, managerial characteristics, and business unit effectiveness at strategy implementation. Academy of Management Journal, 27, 25-41.
16. Henderson, J. C., & Cooprider, J. G. (1990). Dimensions of I/S planning and design aids: A functional model of CASE technology. Information Systems Research, 1(3), 227-254.
17. Iivari, J. (1996). Why are CASE tools not used? Communications of the ACM, 39(10), 94-103.
18. Jauch, L. R., Osborn, R. N., & Glueck, W. F. (1980). Short-term financial success in large business organizations: The environment-strategy connection. Strategic Management Journal, 1, 49-63.
19. Kemerer, C. F. (1992). How the learning curve affects CASE tool adoption. IEEE Software, 9(3), 23-28.
20. Kim, C., & Westin, S. (1988). Software maintainability: Perceptions of EDP professionals. MIS Quarterly, 12(2), 167-185.
21. Letovsky, S. (1987). Cognitive processes in program comprehension. Journal of Systems and Software, 7, 325-339.
22. Letovsky, S., & Soloway, E. (1986). Delocalized plans and program comprehension. IEEE Software, (5), 41-49.
23. Mackay, J. M., & Elam, J. J. (1992). A comparative study of how experts and novices use a decision aid to solve problems in complex knowledge domains. Information Systems Research, 3(2), 150-172.
24. Pennington, N., & Grabowski, B. (1990). The tasks of programming. In Hoc, J.-M., Gréen, T. R. G., Samurcay, R., & Gilmore, D. J. (Eds.), Psychology of Programming (pp. 45-62). London: Academic Press.
25. Prescott, J. E. (1986). Environments as moderators of the relationship between strategy and performance. Academy of Management Journal, 29(2), 329-346.
26. Robbins, S. P. (1997). Essentials of Organizational Behavior. Saddle River, NJ: Prentice Hall.
27. Sawyer, S., & Guinan, P. J. (1998). Software development: Processes and performance. IBM Systems Journal, 37(4), 552-569.
28. Schneberger, S. L. (1993). Software Maintenance: An Update on Issues and Research. Paper presented at the 31st Annual Southeast Conference, Birmingham, Alabama.
29. Schneidewind, N. F. (1987). The state of software maintenance. IEEE Transactions on Software Engineering, SE-13(3), 303-310.
30. Schuler, R. S., & Jackson, S. E. (1996). Human Resource Management: Positioning for the 21st Century (6th ed.). St. Paul, MN: West Publishing.
31. Shaft, T. M., & Vessey, I. (1995). The relevance of application domain knowledge: The case of computer program comrehension. Information Systems Research, 6(3), 286-299.
32. Shaft, T. M., & Vessey, I. (1998). The relevance of application domain knowledge: Characterizing the computer program comprehension process. Journal of Management Information Systems, 15(1), 51-78.
33. Swanson, E. B., & Beath, C. M. (1989). Maintaining Information Systems in Organizations. New York: John Wiley & Sons.
34. Thompson, R. L., Higgins, C. A., & Howell, J. M. (1994). Influence of experience on personal computer utilization: Testing a conceptual model. Journal of Management Information Systems, 11(1), 167-187.
35. Tushman, M. L. (1979). Work characteristics and sub-unit communication structure: A contingency analysis. Administrative Science Quarterly, 24, 82-98.
36. Venkatesh, V., & Davis, F. D. (1994). Modeling the Determinants of Perceived Ease of Use. Paper presented at the International Conference on Information Systems, Vancouver, British Columbia.
37. Venkatesh, V., & Davis, F. D. (1996). A model of the antecedents of perceived ease of use: Development and test. Decision Sciences, 27(3), 451-481.
38. Venkatraman, N. (1989). The concept of fit in strategy research: Toward verbal and statistical correspondence. Academy of Management Review, 14(3), 423-444.
39. Vessey, I. (1986). Expertise in debugging computer programs: An analysis of the content of verbal protocols. IEEE Transactions on Systems, Man, and Cybernetics, SMC-16(5), 621-637.
40. Yau, S. S., & Collofello, J. (1985). Design stability measures for software maintenance. IEEE Transactions on Software Engineering, SE-11(9), 849-856.