Information Systems, Software Engineering, and Systems Thinking: Challenges and Opportunities

International Journal of Information Technologies and Systems Approach (IJITSA)

Volumn 1, Issue 1, 2008, Pages 62-78

  Petkov, Doncho ^a   Edgar Nevill, Denis ^b   Madachy, Raymond ^c   O'connor, Rory ^d  

^a EASTERN CONNECTICUT STATE UNIVERSITY   (United States)

^b CANTERBURY CHRIST CHURCH UNIVERSITY   (United Kingdom)

^c UNIVERSITY OF SOUTHERN CALIFORNIA   (United States)

^d DUBLIN CITY UNIVERSITY   (Ireland)

Author keywords

IS research; software development; software engineering; systems theory; systems thinking

Indexed keywords

EID: 85001544957     PISSN: 1935570X     EISSN: 19355718     Source Type: Journal    
DOI: 10.4018/jitsa.2008010105     Document Type: Article

References (100)

1. Abdel-Hamid, T.K., & Madnick, S.E. (1991). Software project dynamics. Englewood Cliffis, NJ: Prentice Hall.
2. Ackoff, R. (1999). Ackoff's best: His classic writings on management. New York: Wiley.
3. Ackoff, R. (2006). Why few organizations adopt systems thinking. Systems Research and Behavioral Science, 23(5), 705–708.
4. Alter, S. (2002). The work system method for understanding information systems and information systems research. Communications of the AIS, 9(6), 90–104.
5. Alter, S. (2004). Desperately seeking systems thinking in the information systems discipline. In Proceedings of Twenty-Fifth International Conference on Information Systems (pp. 757–769).
6. Alter, S. (2006). The work system method: Connecting people, processes, and IT for business results. Lakspur, CA: Work System Press.
7. Alter, S. (2007). Could the work system method embrace system concepts more fully? Information Resources Management Journal, 20(2), 33–43.
8. Argyris, C., & Schon, D.A. (1978). Organizational learning: A theory of action perspective. Addison-Wesley.
9. Aurum, A., & Wohlin, C. (Eds.). (2005). Engineering and managing software requirements. Heidelberg, Germany: Springer.
10. Avison, D. (2000). Multiview: An exploration in information systems development (2nd ed.). Alfred Waller Ltd.
11. Avison, D.E., & Fitzgerald, G. (2003). Where now for development methodologies? Communications of ACM, 46(1), 79–82.
12. Bajaj, A., Batra, D., Hevner, A., Parsons, J., & Siau, K. (2005). Systems analysis and design: Should we be researching what we teach? Communications of the AIS, 15, 478–493.
13. Baresi, L., Di Nitto, & Ghezzi, C. (2006). Toward open-world software: Issues and challenges. IEEE Computer, 39(10), 36–43.
14. Barton, J., Emery, M., Flood, R.L., Selsky, J., & Wolstenholm, E. (2004). A maturing of systems thinking? Evidence from three perspectives. Systemic Practice and Action Research, 17(1), 3–36.
15. Baskerville, R., & Wood-Harper, A.T. (1998). Diversity in information systems action research methods. European Journal of Information Systems, 7(2), 90–107.
16. Benbasat, I., & Zmud, R. (2003, June). The identity crisis within the IS discipline: Defning and communicating the discipline's core properties. MIS Quarterly, 27(2), 183–194.
17. Bennetts, P.D.C., Wood-Harper, T., & Mills, S. (2000). A holistic approach to the management of information systems development. Systemic Practice and Action Research, 13(2) 189–206.
18. Boehm, B. (2006a). Some future trends and implications for systems and software engineering processes. Systems Engineering, 9(1), 1–19.
19. Boehm, B. (2006b). A view of 20th and 21st century software engineering. In Proceeding of the 28th international conference on Software Engineering. Shanghai, China (pp. 12–29).
20. Boehm, B. (2006c). Educating students in value-based design and development (Keynote address). In Proceedings of the 19th Conference on Software Engineering Education and Training (CSEET).
21. Boehm, B., & Turner, R. (2004). Balancing agility and discipline: A guide for the perplexed. Boston: Addison-Wesley.
22. Boehm, B., & Turner, R. (2005). Management challenges for implementing agile processes in traditional development organizations. IEEE Software, 5, 30–39.
23. Brooks, F.P. (1987). No silver bullet: Essence and accidents of software engineering. In Proceedings of the IFIP 10th World Computing Conference (pp. 1069–1076).
24. Bustard, D.W., & Keenan, F.M. (2005, April 3–8). Strategies for systems analysis: Groundwork for process tailoring. In Proceedings of 12th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 2005), Greenbelt, Maryland (pp. 357–362).
25. Checkland, P. (1999). Systems thinking, systems practice. Chichester: Wiley.
26. Checkland, P., & Holwell, S. (1998). Information, systems and information systems. Chichester: Wiley.
27. Checkland, P., & Poulter, J. (2006). Learning for action: A short defnitive account of soft systems methodology and its use by practitioner, teachers and students. Chichester: Wiley.
28. Chujo, H., & Kijima, K. (2006). Soft systems approach to project-based education and its practice in a Japanese university. Systems Research and Behavioral Science, 23(1), 89–106.
29. Cornford, T., & Smithson, S. (1996). Project research in information systems. MacMillan.
30. Crnkovic, I., Land, R., & Sjögren, A. (2003, March). Is software engineering training enough for software engineers? In Proceedings of the 16th International Conference on Software Engineering Education and Training, Madrid, Spain. IEEE.
31. Denning, P.J. (2005). Recentering computer science. Communications of ACM, 48(11), 15–19.
32. Denning, P.J., & Dunham, R. (2006). Innovation as language action. Communications of ACM, 49(5), 47–52.
33. Developer. (2007). Developer: An online magazine for software developers. Retrieved July 12, 2007, from http://www.developerdotstar.com/mag/categories/systems_software_series.html
34. Dietrich, Y., Floyd, C., & Klichewski, R. (2002). Social thinking-software practice. Boston: MIT Press.
35. Eom, S. (2000). The contribution of systems science to the development of the decision support systems subspecialties: An empirical investigation. Systems Research and Behavioral Science, 17, 117–134.
36. Finnegan, P., Galliers, R.D., & Powell, P. (2002). Planning electronic trading systems: Re-thinking IS practices via triple loop learning. In S. Wrycza (Ed.), Proceedings of the 10th European Conference on Information Systems (pp. 252–261). Retrieved July 12, 2007, from http://www.csrc.lse.ac.uk/asp/aspecis/20020114.pdf
37. Flood, R.L., & Romm, N.R.A. (1996). Diversity management: Triple loop learning. Chichester: Wiley.
38. Glass, R. (2001). Computing failure.com. Upper Saddle River, NJ: Prentice Hall.
39. Glass, R. (2005). Never the CS and IS Twain shall meet? IEEE Software, pp. 120–119.
40. Glass, R., Ramesh, V., & Vessey, I. (2004). An analysis of research in computing disciplines. Communications of ACM, 47(6), 89–94.
41. Gonzales, R. (2005, March-April). Developing the requirements discipline: Software vs. systems. IEEE Software, pp. 59–61.
42. Hevner, A.R., March, S.T., Park, J., & Ram, S. (2004). Design science in information systems research. MIS Quarterly, 28(1), 75–105.
43. Hirschheim, R., & Klein, H.K. (2003). Crisis in the IS field? A critical refection on the state of the discipline. Journal of the Association of Information Systems, 4(5), 237–293.
44. Holwell, S. (2000). Soft systems methodology: Other voices. Systemic Practice and Action Research, 13(6), 773–797.
45. Hughes, J., & Wood-Harper, T. (1999). Systems development as a research act. Journal of Information Technology, 14, 83–94.
46. IbisSoft. (n.d.). Environment that promotes IS research. Retrieved July 12, 2007, from http://www. ibissoft.se/english/index.htm?frameset=research_ frame.htm&itemframe=/english/about_isenvironment.htm
47. Iivari, J., Hirschheim, R., & Klein, H. (2004). Towards a distinctive body of knowledge for information systems experts: Coding ISD process knowledge in two IS journals. Information Systems Journal, 14, 313–342.
48. Iivari, J., & Huisman, M. (2007). The relationship between organizational culture and the deployment of systems development methodologies. MIS Quarterly, 31(1), 35–58.
49. Jackson, M.C. (1992). An integrated programme for critical thinking in information systems research. Journal of Information Systems, 2, 83–94.
50. Jackson, M.C. (2003). Systems thinking: Creative holism for managers. Chichester: Wiley.
51. Jackson, M. C. (2006). Creative holism: A critical systems approach to complex problem situations. Systems Research and Behavioral Science, 23(5), 647–657.
52. Kroes, P., Franssen, M., van de Poel, I., & Ottens, M. (2006). Treating socio-technical systems as engineering systems: Some conceptual problems. Systems Research and Behavioral Science, 23(6), 803–814.
53. Kruchten, P. (2005, March-April). Casting software design in the function-behavior-structure framework. IEEE Software, pp. 52–58.
54. Kuhn, T.S. (1970). The structure of scientifc revolutions (2nd ed.). Chicago: University of Chicago Press.
55. Lane, J.A., & Boehm, B. (2007). System-of-systems cost estimation: Analysis of lead system integrator engineering activities. Information Resources Management Journal, 20(2), 23–32.
56. Laware, J., Davis, B., & Peruisch, K. (2006). Systems thinking: A paradigm for professional development. The International Journal of Modern Engineering, 6(2).
57. Lee, A. (2000, May). 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 (Keynote address). In Proceedings of the 11th International Conference on Information Management, Taiwan. Retrieved July 12, 2007, from http://www.people.vcu.edu/aslee/ICIM-key-note-2000
58. Lee, A. (2004). Thinking about social theory and philosophy for information systems. In J. Mingers & L. Willcocks (Eds.), Social theory and philosophy for information systems (pp. 1–26). Chichester: Wiley.
59. Lee, B., & Miller, J. (2004). Multi-project software engineering analysis using systems thinking. Software Process: Improvement and Practice, 9(3).
60. Lewis, P. (1995). New challenges and directions for data analysis and modeling. In F. Stowell (Ed.), Information systems provision: The contribution of soft systems methodology (pp. 186–205). London: McGraw-Hill.
61. Linstone, H.A. (1984). Multiple perspectives for decision making: Bridging the gap between analysis and action. New York: North Holland.
62. Madachy, R.J. (2006). Integrated modeling of business value and software processes. Lecture Notes in Computer Science, 3840, 389–402.
63. Madachy, R.J. (2007). Software process dynamics. Wiley/IEEE Press.
64. Madachy, R.J., Boehm, B., & Lane, J.A. (2007). Software lifecycle increment modeling for new hybrid processes. In Software process improvement and practice. Wiley. Retrieved July 12, 2007, from http:/6/dx.doi.org/10.1002/spip.332
65. Mason, R., & Mitroff, I. (1981). Challenging strategic planning assumptions. New York: Wiley.
66. Mathieu, R.G. (2002). Top-down approach to computing. IEEE Computer, 35(1), 138–139.
67. McLeod, R. (1995). Systems theory and information resources management: Integrating key concepts. Information Resources Management Journal, 8(2), 5–14.
68. Mingers, J. (1995). Using soft systems methodology in the design of information systems. In F. Stowell (Ed.), Information systems provision: The contribution of soft systems methodology (pp. 18–50). London: McGraw-Hill.
69. Mingers, J. (2001). Multimethodology: Mixing and matching methods. In J. Rosenhead & J. Mingers (Eds.), Rational analysis for a problematic world revisited. Chichester: Wiley.
70. Mitroff, I., & Linstone, H. (1993). The unbounded mind. New York/Oxford: Oxford University Press.
71. Mora, M., Gelman, O., Forgionne, G., Petkov, D., & Cano, J. (2007). Integrating the fragmented pieces of IS research paradigms and frameworks: A systems approach. Information Resource Management Journal, 20(2), 1–22.
72. Ngwenyama, O.K., & Lee, A.S. (1997). Communication richness in electronic mail: Critical social theory and the contextuality of meaning. MIS Quarterly, 21(2), 145–167.
73. Petkov, D., Petkova, O., Andrew, T., & Nepal, T. (in print). Mixing multiple criteria decision making with soft systems thinking techniques for decision support in complex situations. Decision Support Systems.
74. Petkova, O., & Roode, J.D. (1999). An application of a framework for evaluation of factors affecting software development productivity in the context of a particular organizational environment. South African Computing Journal, 24, 26–32.
75. Pfleeger, S.L. (2001). Software engineering theory and practice. Upper Saddle River, NJ: Prentice Hall.
76. Pressman, R. (2001). Software engineering: A practitioner's approach (5th ed.). New York: McGraw-Hill.
77. QAA. (2007). Subject benchmark statements: Computing. Quality Assurance Agency. Retrieved July 12, 2007, from http://www.qaa.ac.uk/academicin-frastructure/benchmark/statements/
78. Reifer, D. (2003, November-December). Is the software engineering state of the practice getting closer to the of the art? IEEE Software, 20(6), 78–83.
79. Richmond, B. (1994, July). System dynamics/systems thinking: Let's just get on with it. In Proceedings of the 1994 International System Dynamics Conference, Sterling, Scotland. Retrieved July 12, 2007, from http://www.hps-inc.com/st/paper.html
80. Saaty, T. (1990). Multicriteria decision making: The analytic hierarchy process (2nd ed.). Pittsburgh: RWS Publications.
81. Sage, A.P. (2005). Systems of systems: Architecture based systems design and integration (Keynote address). In Proceedings of the International Conference on Systems, Man and Cybernetics, Hawaii.
82. Sewchurran, K., & Petkov, D. (2007). A systemic framework for business process modeling combining soft systems methodology and UML. Information Resources Management Journal, 20(3), 46–62.
83. Sommerville, I. (2007). Software engineering (8th ed.). Harlow: Pearson.
84. Stowell, F. (Ed.). (1995). Information systems provision: The contribution of soft systems methodology. London: McGraw-Hill.
85. Stowell, F., & West, D. (1996). Systems thinking, information systems practice. In Proceedings of the 40th Conference of the International Society for Systems Sciences, Budapest, Hungary.
86. SWEBOK. (2004). Software engineering body of knowledge defned by the IEEE CS and ACM. Retrieved July 12, 2007, from http://www.swebok. org/ironman/pdf/SWEBOK_Guide_2004.pdf
87. Sweeney, A., & Bustard, D.W. (1997). Software process improvement: Making it happen in practice. Software Quality Journal, 6, 265–273.
88. Ulrich, W. (1998). Systems thinking as if people mattered: Critical systems thinking for citizens and managers (Working paper no. 23). Lincoln School of Management.
89. Valerdi, R., & Madachy, R. (2007). Impact and contributions of MBASE on software engineering graduate courses. Journal of Systems and Software, 80(8), 1185–1190.
90. Van Vilet. (2000). Software engineering: Principles and practices. Wiley.
91. Vo, H.V., Paradice, D., & Courtney, J. (2001). Problem formulation in inquiring organizations: A multiple perspectives approach. In Proceedings of the 7th Americas Conference on Information Systems, Boston, Massachusetts.
92. Vo, H.V., Chae, B., & Olson, D.L. (2006). Integrating systems thinking into IS education. Systems Research and Behavioral Science, 23(1), 107–122.
93. Weinberg, G. (1992). Quality software management (Vol. 1: Systems Thinking). New York: Dorset House Publishing.
94. Weinberg, G. (2007). A site for books, articles and courses. Retrieved July 12, 2007, from http://www.geraldmweinberg.com/
95. Wendorff, P. (2002). Systems thinking in extreme programming. In Proceedings of the 10th European Conference on Information Systems (pp. 203–207). Retrieved July 12, 2007, from http://www.csrc.lse. ac.uk/asp/aspecis/20020124.pdf
96. White, L., & Tacket, A. (1996). The end of theory? Omega, 24(1), 47–56.
97. Wilson, B. (1990). Systems: Concepts, methodologies and applications (2nd ed.). Chichester: Wiley.
98. Xu, L.D. (2000). The contribution of systems science to information systems research. Systems Research and Behavioral Science, 17(2), 105–116.
99. Yourdon, E. (2007). A site for books, articles and blogs. Retrieved July 12, 2007, from http://www. yourdon.com
100. Zhu, Z. (2006). Complementarism versus pluralism: Are they different and does it matter? Systems Research and Behavioral Science, 23(6), 757–770.