Building the it workforce of the future: The demand for more complex, abstract, and strategic knowledge

Information Resources Management Journal

Volumn 21, Issue 2, 2008, Pages 63-79

  Armstrong, Deborah J ^a   Nelson, H James ^b   Nelson, Kay M ^b   Narayanan, V K ^c  

^a FLORIDA STATE UNIVERSITY   (United States)

^b SOUTHERN ILLINOIS UNIVERSITY   (United States)

^c DREXEL UNIVERSITY   (United States)

Author keywords

Future of is; Is personnel; Is skill requirements

Indexed keywords

SOFTWARE ENGINEERING;

CAUSAL MAPPING; COGNITIVE MAPS; IS PERSONNEL; SKILL REQUIREMENTS; SOFTWARE DEVELOPMENT PROCESS; STATE OF THE ART; STRATEGIC KNOWLEDGE; THOUGHT PROCESS;

SOFTWARE DESIGN;

EID: 70249131561     PISSN: 10401628     EISSN: 15337979     Source Type: Journal    
DOI: 10.4018/irmj.2008040104     Document Type: Article

References (66)

1. Abdolmohammadi, M. J., & Shanteau, J. (1992). Personal attributes of expert auditors. Organizational Behavior and Human Decision Processes, 53(2), 158-172.
2. Adams, J., Koushik, S., Vasudeva, G., & Galambos, G. (2001). Patterns for e-business: A strategy for reuse. Double Oak, TX: IBM Press.
3. Adelson, B. (1981). Problem solving and the development of abstract categories in programming languages. Memory and Cognition, 9(4), 422-433.
4. 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.
5. Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M., I., F.-K., & Angel, S. (1977). A pattern language. New York: Oxford University Press.
6. Axelrod, R. (Ed.). (1976). Structure of decision: The cognitive maps of political elites. Princeton, NJ: Princeton University Press.
7. Batra, D. a. D., J. G. (1992). Conceptual data modeling in database design: Similarities and differences between expert and novice designers. International Journal Man-Machine Studies, 37, 83-101.
8. Bedard, J. (1991). Expertise and its relation to audit decision quality. Contemporary Accounting Research, 8(1), 198-222.
9. Boehn-Davis, D. A., & Ross, L. S. (1992). Program design methodologies and the development process. International Journal Man-Machine Studies, 36, 1-19.
10. Booch, G., Rumbaugh, J., & Jacobson, I. (1999). The unified modeling language user guide. Reading, MA: Addison-Wesley.
11. Bougon, M., Weick, K., & Binkhorst, D. (1977). Cognition in organizations: An analysis of the Utrecht Jazz Orchestra. Administrative Science Quarterly, 22, 606-639.
12. Brown, D. (1977). An introduction to object oriented analysis: Objects in plain English. New York: Wiley.
13. Brown, L. T., & Stanners, R. F. (1983). The assessment and modification of concept interrelationships. Journal of Experimental Education, 52, 11-21.
14. Carley, K., & Palmquist, M. (1992). Extracting, representing, and analyzing mental models. Social Forces, 70, 601-636.
15. Coad, P., & Yourdon, E. (1991). Object-oriented design. Englewood Hills, NJ: Prentice-Hall.
16. Crowder, R. G. (1976). Principles of learning and memory. Hillsdale: Erlbaum.
17. Davenport, T. (2000). Mission critical: Realizing the promise of enterprise systems. Cambridge: Harvard Business School Press.
18. Eden, C., Jones, S., Sims, D., & Smithin, T. (1981). The intersubjectivity of issues and issues of intersubjectivity. Journal of Management Studies, 18(1), 37-47.
19. Evernden, R. (1996). The information framework. IBM System Journal, 35(1), 37-69.
20. Ezingeard, J., & Chandler-Wilde, R. (1999, November 1999). Evaluating how ERP can provide competitive advantage: Basis for a research framework. Paper presented at the Sixth European Conference on IT Evaluation, Brunel University.
21. Faraj, S., & Sproull, L. S. (2000). Coordinating expertise in software development teams. Management Science, 46(12), 1554-1568.
22. Fichman, R. G., & Kemerer, C. F. (1992). Objectoriented and conventional analysis and design methodologies: comparison and critique. IEEE Computer, 25(10), 22-39.
23. Fiol, C. M., & Huff, A. S. (1992). Maps for managers: Where are we? Where do we go from here? Journal of Management Studies, 29(3), 267-285.
24. Ford, J. D., & Hegarty, W. H. (1984). Decision maker's beliefs about the causes and effects of structure: An exploratory study. Academy of Management Journal, 27(2), 271-291.
25. Geelsin, W. E., & Shavelson, R. (1975). Comparison of content structure and cognitive structure in high school students' learning of probability. Journal of Research in Mathematics Education, 6, 109-120.
26. Glaser, R. J., & Chi, M. T. (1988). Overview. In M. T. Chi, R. J. Glaser, & M. J. Farr (Eds.), The nature of expertise. Hillsdale, NJ: Erlbaum.
27. Huff, A. S. (1990). Mapping strategic thought. Chicester, UK: John Wiley & Sons Ltd.
28. Iivari, J. (1995). Object orientation as structural, functional, and behavioural modelling: A comparison of six methods of object oriented analysis. Information and Software Technology, 37(3), 155-163.
29. Jacobs-Lawson, J. M., & Hershey, D. A. (2002). Concept maps as an assessment tool in psychology courses. Teaching of Psychology, 29(1), 25-29.
30. Johnson, R. E. (1997). Frameworks = patterns + components. Communications of the ACM, 40(10), 39-42.
31. Johnson, R., Hardgrave, B. C., & Doke, E. R. (1999). An industry analysis of developer beliefs about object-oriented systems development. The DATA BASE for Advances in Information Systems, 30(1), 47-64.
32. Knoke, D., & Kuklinski, J. H. (1982). Network analysis. Newbury Park: Sage.
33. Korson, T., & McGreggor, J. D. (1990). Understanding object-oriented: A unifying approach. Communications of the ACM, 33(9), 40-60.
34. Koubek, R. J., Salvendy, G., Dunsmore, H. E., & LeBold, W. K. (1989). Cognitive issues in the process of software development: Review and reappraisal. International Journal Man-Machine Studies(30), 171-191.
35. Kraiger, K., Ford, K. J., & Salas, E. (1993). Application of cognitive, skill based and affective theories of learning outcomes to new methods of training evaluation. Journal of Applied Psychology, 78, 311-328.
36. Lee, A., & Pennington, N. (1994). The effects of paradigm on cognitive activities in design. International Journal on Human-Computer Studies, 40, 577-601.
37. Lee, J., Siau, K., & Hong, S. (2003). Enterprise integration with ERP and EAI. Communications of the ACM, 46(2), 54-60.
38. Lincoln, Y. S., & Guba, E. G. (1985). Naturalistic inquiry. Newbury Park: Sage.
39. Luftman, J. F., & Brier, T. (1999). Achieving and sustaining business-IT alignment. California Management Review, 42(1), 109-123.
40. Luftman, J. N. (Ed.). (1996). Competing in the information age: Strategic alignment in practice. New York: Oxford University Press.
41. Martin, J., & McClure, C. (1988). Structured techniques: A basis for CASE. Englewood Cliffs: Prentice Hall.
42. McKeithen, K., Reitman, J., Rueter, H. H., & Hirtle, S. (1981). Knowledge organization and skill differences in computer programmers. Cognitive Psychology, 13, 307-325.
43. Morris, M. G., Speier, C., & Hoffer, J. A. (1999). An examination of classical and object-oriented systems analysis methods: Does prior experience help or hinder performance? Decision Sciences, 30(1), 107-136.
44. Nadkarni, S., & Narayanan, S. (2005). Validity of the structural properties of text-based causal maps: An empirical assessment. Organizational Research Methods, 8(1), 9-40.
45. Narayanan, V. K. (2005). Causal mapping: A historical overview. In V. K. Narayanan & D. Armstrong (Eds.), Causal mapping for research in information technology. Hershey, PA: IGI Global.
46. Narayanan, V.K., and Armstrong, D.J. (2005)(eds.) Causal Mapping for Research in Information Technology, Hershey, PA: IGI Global.
47. Narayanan, V. K., & Fahey, L. (1990). Evolution of Revealed Causal Maps During Decline: A Case Study of Admiral. In A. Huff (Ed.), Mapping Strategic Thought. London: John Wiley and Sons.
48. Nelson, H. J., Armstrong, D., & Ghods, M. (2002). Old dogs and new tricks. Communications of the ACM, 45(10), 132-137.
49. Nelson, H. J., Irwin, G., & Monarchi, D. E. (1997). Journeys up the mountain: Different paths to learning object oriented technology. Accounting, Management, and Information Technologies, 7(1).
50. Nelson, K. M., Nadkarni, S., Narayanan, V. K., & Ghods, M. (2000). Understanding software operations support expertise: A revealed causal mapping approach. MIS Quarterly, 24(3), 475-507.
51. Nelson, K. M., & Nelson, H. J. (2003). The need for a strategic ontology. Paper presented at the MISQ Special Issue Workshop: Standard Making, A Critical Frontier for Information Systems, Seattle.
52. Pennington, N. (1987). Stimulus structures and mental representations in expert comprehension of computer programs. Cognitive Psychology, 19, 295-341.
53. Richardson, G. L., Butler, C. W., & Tomlinson, J. D. (1980). A primer on structured program design. New York: Petrocelli Books.
54. Rossi, P., Wright, J., & Anderson, A. (1983). Handbook of research methods. Orlando: Academic Press.
55. Rosson, M., & Alpert, S. R. (1990). The cognitive consequences of object-oriented design. Human Computer Interaction, 5, 345-379.
56. Schmidt, D. C. (1996). Using design patterns to guide the development of reusable object-oriented software. ACM Computing Surveys, 28(4).
57. Shanteau, J. (1987). Psychological characteristics of expert decision makers. In J. L. Mumpower, O. Renn, L. D. Phillips, & V. R. Uppuluri (Eds.), Expert judgment and expert systems (pp. 289-304). Berlin: Springer-Verlag.
58. Shanteau, J. (1992). Competence in experts: The role of task characteristics. Organizational Behavior and Human Decision Processes, 53, 252-266.
59. Sheetz, S. D. (2002). Identifying the difficulties of object oriented development. The Journal of Systems and Software, 64(1), 23-30.
60. Sheetz, S. D., & Teagarden, D. P. (2001). Illustrating the cognitive consequences fo object oriented systems development. The Journal of Systems and Software, 59, 163-179.
61. Shull, F., Lanubile, F., & Basili, V. (2000). Investigating reading techniques for object oriented framework learning. IEEE Transactions on Software Engineering, 26(11), 1101-1118.
62. Sircar, S., Nerur, S., & Mahapatra, R. K. (2001). Revolution or evolution? A comparison of object oriented and structred methods. MIS Quarterly, 25(4), 457-471.
63. Sudman, S. (1976). Applied sampling. New York: Academic Press, Inc.
64. Sumner, M. (2000). Risk factors in enterprise-wide/ ERP projects. Journal of Information Technology, 15(4), 317-327.
65. Vitalari, N. P. (1985). Knowledge as a basis for expertise in systems analysis: An empirical study. Management Information Systems Quarterly, 9(3), 221-241.
66. Xing, Z., & Stroulia, E. (2005). Analyzing the evolutionary history of the logical design of objectoriented software. IEEE Transactions on Software Engineering, 31(10), 850-868.