Toward an interdisciplinary engineering and management of complex IT-intensive organizational systems: A systems view

Emerging Systems Approaches in Information Technologies: Concepts, Theories, and Applications

Volumn , Issue , 2009, Pages 1-24

  Mora, Manuel ^a   Gelman, Ovsei ^b   Frank, Moti ^c   Paradice, David B ^d   Cervantes, Francisco ^b   Forgionne, Guisseppi A ^e  

^a UNIVERSIDAD AUTÓNOMA DE AGUASCALIENTES   (Mexico)

^b UNIVERSIDAD NACIONAL AUTÓNOMA DE MÉXICO   (Mexico)

^c HOLON INSTITUTE OF TECHNOLOGY   (Israel)

^d FLORIDA STATE UNIVERSITY   (United States)

^e UNIVERSITY OF MARYLAND BALTIMORE COUNTY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84900596227     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.4018/978-1-60566-976-2.ch001     Document Type: Chapter

References (105)

1. Ackoff, R. (1960). Systems, organizations and interdisciplinary research. General System Yearbook, 5, 1-8.
2. Ackoff, R. (1967). Management misinformation systems. Management Science, 14(4), 147-156.
3. Ackoff, R. (1971). Towards a system of systems concepts. Management Science, 17(11), 661-671.
4. Ackoff, R. (1973). Science in the Systems Age: Beyond IE, OR, and MS. Operations Research, May-Jun, 661-671.
5. Alter, S. (2001). Are the fundamental concepts of information systems mostly about work systems? CAIS, 5(11), 1-67.
6. Alter, S. (2003). 18 reasons why IT-reliant work systems should replace "the IT artifact" as the core subject matter of the IS field. CAIS, 12(23), 366-395.
7. Alter, S. (2007). Could the work system method embrace systems concepts more fully? Information Resources Management Journal, 20(2), 33-43.
8. Andriole, S., & Freeman, P. (1993, May). Software systems engineering: The case for a new discipline. Software Engineering Journal, pp. 165-179.
9. Arnold, S., & Lawson, H.W. (2004). Viewing systems from a business management perspective: The ISO/IEC 15288 standard. Systems Engineering, 7(3), 229-242.
10. Avison, D., Wood-Harper, A., Vidgen, R., & Wood, J. (1998). A further exploration into information systems development: The evolution of multiview2. Information Technology & People, 11(2), 124-139.
11. Bacon, J., & Fitzgerald, B. (2001). A systemic framework for the field of information systems. The DATA BASE for Advances in Information Systems, 32(2), 46-67.
12. Bar-Yam, Y. (2003a). When systems engineering fails: Toward complex systems engineering. In Proceedings of the International Conference on Systems, Man & Cybernetics (pp. 2021-2028). Piscataway, NJ: IEEE Press.
13. Bar-Yam, Y. (2003b). Unifying principles in complex systems. In M.C. Roco & W.S. Bainbridge (Eds.), Converging technology (NBIC) for improving human performance (pp. 1-32). Kluwer.
14. Bar-Yam, Y. (2005). About engineering complex systems: multiscale analysis and evolutionary engineering. In S. Brueckner et al. (Eds.), ESOA 2004, Heidelberg, Germany (pp. 16-31). Springer-Verlag. Lecture Notes in Computer Science, 3464.
15. Bate, R. (1998, July-August). Do systems engineering? Who, me? IEEE Software, pp. 65-66.
16. Beachboard, J., & Beard, D.(2005). Innovation in information systems education-II: Enterprise IS management: A capstone course for undergraduate IS majors. CAIS, 15, 315-330.
17. Beckerman, L. (2000). Application of complex systems science to systems engineering. Systems Engineering, 3(2), 96-102.
18. Boehm, B. (2000, March). Unifying software engineering and systems engineering. Computer, pp. 114-116.
19. Boehm, B. (2006). Some future trends and implications for systems and software engineering processes. Systems Engineering, 9(1), 1-19.
20. Boehm, B., & Lane, J. (2006, May). 21st century processes for acquiring 21st century software-intensive systems of systems. Crosstalk: The Journal of Defense Software Engineering, pp. 1-9.
21. Brown, D., & Scherer, W. (2000). A comparison of systems engineering programs in the United States. IEEE Transactions on Systems, Man and Cybernetics (Part C: Applications and Reviews), 30(2), 204-212.
22. Buede, E. (2000). The engineering design of systems (Wiley Series in Systems Engineering). New York: Wiley.
23. Calvano, C., & John, P. (2004). Systems engineering in an age of complexity. Systems Engineering Journal, 7(1), 25-34.
24. Carlock, P., & Fenton, R. (2001). System of systems (SoS) enterprise system engineering for information-intensive organizations. Systems Engineering, 4(4), 242-261.
25. Carr, N. (2003). IT doesn't matter. Harvard Business Review, 81(5), 41-49.
26. Checkland, P. (2000). Soft systems: A 30-year retrospective. In P. Checkland (Ed.), Systems thinking, systems practice (pp. A1-A65). Chichester, UK: Wiley.
27. Checkland, P., & Holwell, S. (1995). Information systems: What's the big idea? Systemist, 7(1), 7-13.
28. Chesbrough, C., & Spohrer, J. (2006). A research manifesto for services science. Communications of the ACM, 49(7), 35-40.
29. CIO UK Web site. (2007). Late IT projects equals lower profits. Retrieved July 10, 2007, from http://www.cio.co.uk/concern/resources/news/index.cfm?articleid=1563
30. Cleary, D. (2005). Perspectives on complex-system engineering. MITRE Systems Engineering Process Office Newsletter, 3(2), 1-4.
31. Culnan, M., & Swason, B. (1986). Research in management information systems 1980-1984: Points of work and reference. MIS Quarterly, 10(3), 289-302.
32. Curtis, B., Krasner, H., & Iscoe, N. (1988). A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268-1287.
33. Demirkan, H., & Goul, M. (2006). AMCIS 2006 panel: Towards the service oriented enterprise vision: Bridging industry and academics. CAIS, 18, 546-556.
34. Denning, P., Comer, D., Gries, D., Mulder, M., Tucker, A., Turner, J., & Young, P. (1989). Computing as discipline. Communications of the ACM, 32(1), 9-23.
35. Denno, P., & Feeney, A. (2002). Systems engineering foundations of software systems integration. In J.-M. Bruel & Z. Bellahsène (Eds.), OOIS 2002 Workshops, Heidelberg, Germany (pp. 245-259). Springer. Lecture Notes in Computer Science, 2426.
36. Dugmore, J. (2006, May). Benchmarking provision of IT services. ISO Focus, pp. 48-51.
37. Editorial policy statement. (2006). MIS Quarterly, 23(1), iii.
38. Emes, M., Smith, A., & Cowper, D. (2001). Confronting an identity crisis: How to "brand" systems engineering. Systems Engineering, 8(2), 164-186.
39. Ewusi-Mensah, K. (1997). Critical issues in abandoned information systems development projects. Communications of the ACM, 40(9), 74-80.
40. Farhoomand, A., & Drury, D. (1999). A historiographical examination of information systems. CAIS, 1(19), 1-27.
41. Farr, J., & Buede, D. (2003). Systems engineering and engineering management: Keys to the efficient development of products and services. Engineering Management Journal, 15(3), 3-9.
42. Feingenbaum, D. (1968). The engineering and management of an effective system. Management Science, 14(12), 721-730.
43. Frank, M., & Waks, S. (2001). Engineering systems thinking: A multifunctional definition. Systemic Practice and Action Research, 14(3), 361-379.
44. Franke, M. (2001). The engineering of complex systems for the future. Engineering Management Journal, 13(12), 25-32.
45. Fuggetta, A.(2000). Software process: A road-map. In Proceedings of the ICSE International Conference on Software Engineering, Limerick, Ireland (pp. 25-34). ACM Digital Library.
46. Gelman, O., Mora, M., Forgionne, G., & Cervantes, F. (2005). Information systems and systems theory. In M. Khosrow-Pour (Ed.), Encyclopedia of information science and technology (vol. 3, pp. 1491-1496). Hershey, PA: Idea Group.
47. Gill, G. (1995). Early expert systems: Where are they now? MIS Quarterly, 19(1), 51-81.
48. Glass, R.(1998). Software runaways. London: Prentice.
49. Glass, R., Ramesh, V., & Vessey, I. (2004). An analysis of research in computing disciplines. Communications of the ACM, 47(6), 89-94.
50. Glass, R., Vessey, I., & Ramesh, V. (2002). Research in software engineering: An analysis of literature. Information & Software Technology, 44(8), 491-506.
51. Gorgone, J., Gray, P., Stohr, E., Valacich, J., & Wigand, R. (2006). MSIS 2006: Model curriculum and guidelines for graduate degree programs in information systems. CAIS, 17, 1-56.
52. Goul, M., Henderson, J., & Tonge, F. (1992). The emergence of artificial intelligence as a reference discipline for decision support systems. Decision Sciences, 11(2), 1273-1276.
53. Hecht, H. (1999, March). Systems engineering for software-intensive projects. In Proceedings of the ASSET Conference, Dallas, Texas (pp. 1-4).
54. Hevner, A., & March, S. (2003, November). The information systems research cycle. Computer, pp. 111-113.
55. Hevner, A., March, S., Park, J., & Ram, S. (2004). Design science in information systems research. MIS Quarterly, 21(8), 75-105.
56. Hitchins, D.K. (2003). Advanced systems thinking, engineering and management. London: Attach House.
57. Hole, E., Verma, D., Jain, R., Vitale, V., & Popick, P. (2005). Development of the ibm.com interactive solution marketplace (ISM): A systems engineering case study. Systems Engineering, 8(1), 78-92.
58. Honour, E. (2004). Understanding the value of systems engineering. In Proceedings of the INCOSE Conference (pp. 1-16). INCOSE.
59. IEEE. (2001). SWEBOK: Guide to the software engineering body of knowledge. Los Alamitos, CA: IEEE Computer Society Press.
60. INCOSE. (2004). Systems engineering handbook. Author.
61. Industry Report. (2005). Facility considerations for the data center version 2.1 (White paper). APC and PANDUIT Companies. Retrieved July 10, 2007, from http://www.apc.com
62. Ives, B., Hamilton, S., & Davis, G. (1980). A framework for research in computer-based management information systems. Management Science, 26(9), 910-934.
63. Jackson, M. (1991). Systems methodology for the management sciences. New York: Plenum.
64. Johnson, K., & Dindo, J. (1998). Expanding the focus of software process improvement to include systems engineering. Crosstalk: The Journal of Defense Software Engineering, 1-13.
65. Keating, C., Rogers, R., Unal, R., Dryer, D., Sousa-Poza, A., Safford, R., Peterson, W., & Rabadi, G. (2003). System of systems engineering. Engineering Management, 15(3), 36-45.
66. Kellner, M., Curtis, B., deMarco, T., Kishida, K., Schulemberg, M., & Tully, C. (1991). Nontechnological issues in software engineering. In Proceedings of the 13th ICSE International Conference on Software Engineering (pp. 149-150). ACM Digital Library.
67. Kitchenham, B., et al. (2002). Preliminary guidelines for empirical research in software engineering. IEEE Transactions on Software Engineering, 28(8), 721-734.
68. Kwon, T., & Zmud, R. (1987). Unifying the fragmented models of information systems implementation. In J. Boland & R. Hirshheim (Eds.), Critical issues in information systems research (pp. 227-251). New York: John Wiley.
69. Lee, A. (2000). Systems thinking, design science and paradigms: Heeding three lessons from the past to resolve three dilemmas in the present to direct a trajectory for future research in the information systems field. Retrieved July 10, 2007, from http://www.people.vcu.edu/~aslee/ICIM-keynote-2000/ICIM-keynote-2000.htm
70. Madachy, R. (1996). Modeling software processes with system dynamics: Current developments. In Proceedings of the System Dynamics Conference (pp. 1-23). Cambridge, MA: Systems Dynamic Society.
71. Magee, C., & de Weck, O. (2004). Complex system classification. In Proceedings of the 14th Annual INCOSE International Symposium of the International Council on Systems Engineering (pp. 1-18). INCOSE.
72. March, S., & Smith, G. (1995). Design and natural science research on information technology. Decision Support Systems, 15, 251-266.
73. Mingers, J. (2000). The contributions of critical realism as an underpinning philosophy for OR/MS and systems. Journal of the Operational Research Society, 51, 1256-1270.
74. Mingers, J. (2001). Combining IS research methods: Towards a pluralist methodology. Information Systems Research, 12(3), 240-253.
75. Mingers, J. (2002). Realizing information systems: Critical realism as an underpinning philosophy for information systems. In Proceedings of the 23rd ICIS International Conference in Information Systems (pp. 295-303).
76. Mingers, J. (2003). A classification of the philosophical assumptions of management science methodologies. Journal of the Operational Research Society, 54(6), 559-570.
77. Mora, M., Cervantes, F., Gelman, O., Forgionne, G., & Cano, J. (2006b). The interaction of systems engineering, software engineering and information systems disciplines: A system-oriented view. In Proceedings of the 18th International Conference on Systems Research, Informatics and Cybernetics, Baden-Baden, Germany (pp. 1-5).
78. Mora, M., Gelman, O., Cano, J., Cervantes, F. & Forgionne, G. (2006a). Theory of systems and information systems research frameworks. Proceedings from the 50th Annual Meeting of the International Society for the Systems Sciences, paper 2006-282, (1-7), Somona State University, CA.
79. Mora, M., Gelman, Cervantes, F., Mejia, M., & Weitzenfeld, A. (2003). A systemic approach for the formalization of the information system concept: Why information systems are systems. In J. Cano (Ed.), Critical reflections of information systems: A systemic approach (pp. 1-29). Hershey, PA: Idea Group.
80. Mora, M., Gelman, O., Forgionne, G., Petkov, D., & Cano, J. (2007a). Integrating the fragmented pieces of IS research paradigms and frameworks: A systems approach. Information Resources Management Journal, 20(2), 1-22.
81. Mora, M., Gelman, O., Macias, J. & Alvarez, F. (2007c). The management and engineering of IT-intensive systems: a systemic oriented view. Proceedings from the 2007 IRMA International Conference, (1448-1453), Vancouver, BC, Canada: Idea Group.
82. Mora, M., Gelman, O., O'Connor, R., Alvarez, F., & Macías, J. (2007b). On models and standards of processes in SE, SwE and IT&S disciplines: Toward a comparative framework using the systems approach. In K. Dhanda & R. Hackney (Eds.), Proceedings of the ISOneWorld 2007 Conference: Engaging Academia and Enterprise Agendas. Information Institute. Track in System Thinking/Systems Practice, Las Vegas, USA, April 11-13, 2007, paper-49, 1-18.
83. Mulder, M., et al. (1999). ISCC'99: An information systems-centric curriculum '99: program guidelines for educating the next generation of information systems specialists, in collaborating with industry. Retrieved July 10, 2007, from http://www.iscc.unomaha.edu
84. Nolan, R., & Wetherbe, J. (1980, June 1). Toward a comprehensive framework for MIS research. MIS Quarterly, pp. 1-20.
85. Nunamaker, J., Chen, T., & Purdin, T. (1991). Systems development in information systems research. Journal of Management Information Systems, 7(3), 89-106.
86. OECD. (2004). Highlights of the OECD information technology outlook 2004. Retrieved July 10, 2007, from http://www.oecd.org
87. Orlikowski, W., & Iacono, S. (2001). Desperately seeking the IT in IT research. Information Systems Research, 7(4), 400-408.
88. Prewitt, E., & Cosgrove, L. (2006). The state of the CIO 2006 (CIO Report pp. 1-8). Retrieved July 10, 2007, from http://www.cio.com/state
89. Rittel, H., & Weber, M. (1973). Dilemmas in a general theory of planning. Policy Sciences, 4, 155-169.
90. Sage, A. (2000). Systems engineering education. IEEE Transactions on Systems, Man and Cybernetics (Part C: Applications and Reviews), 30(2), 164-174.
91. Sage, A., & Cuppan, D. (2001). On the systems engineering and management of systems of systems and federations of systems. Information, Knowledge, Systems Management, 2, 325-345.
92. SEI. (2003). SEI annual report 2003. Pittsburgh: Software Engineering Institute.
93. Shenhar, A., & Bonen, Z. (1997). The new taxonomy of systems: Toward an adaptive systems engineering framework. IEEE Transactions on Systems, Man and Cybernetics (Part A: Systems and Humans), 27(2), 137-145.
94. Simon, H. A. (1969). The sciences of the artificial. Cambridge, MA: MIT Press.
95. Sommerville, I. (1998). Systems engineering for software engineers. Annals of Software Engineering, 6, 111-129.
96. Sowa, J., & Zachman, J. (1992). Extending and formalizing the framework for information systems architecture. IBM Systems Journal, 31(3), 590-616.
97. Standish Group International. (2003). The extreme CHAOS report. Author.
98. Sterman, J. (2001). Systems dynamic modeling: Tools for learning in a complex world. California Management Review, 43(4), 8-25.
99. Thayer, R. (1997). Software systems engineering: An engineering process. In R. Thayer & M. Dorfan (Eds.), Software requirements engineering (pp. 84-109). Los Alamitos, CA: IEEE Computer Society Press.
100. Thayer, R. (2002, April). Software systems engineering: A tutorial. IEEE Computer, pp. 68-73.
101. van Bon, J., Pieper, M., & van deer Veen, A. (2006). Foundations of IT service management, based in ITIL. San Antonio, TX: Van Haren.
102. Vessey, I., Ramesh, V., & Glass, R. (2002). Research in information systems: An empirical study of diversity in the discipline and its journals. Journal of Management Information Systems, 19(2), 129-174.
103. von Bertalanffy, L. (1972, December). The history and status of general systems theory. Academy of Management Journal, pp. 407-426.
104. Wallace, L., & Keil, M. (2004). Software project risks and their effect on outcomes. Communications of the ACM, 47(4), 68-73.
105. Zachman, J. (1987). A framework for information systems architecture. IBM Systems Journal, 26(3), 276-292.