Author

Assistant Professor, AllamehTabataba’iUniversity,Tehran, Iran

Abstract

Effect of management, organization and technology factors on the success or failure of information systems in organizations and institutions in the country, including issues and topics that information systems and information technology researchers always focus on them. Unfortunately in our country researchers fail to recognize the identity of a computer system failure. Knowledge of the reasons for failure of a computerized information system, causing unconsciousness and awareness in managers and design team and focus on the weaknesses will be possible. Managers support in strengthening progression factors and weakening preventing factors in the design, implementation and development of information systems and prepared infrastructure, including hardware and software can be key points of preventing of failure and success of an information system.
The research is an applied research and its nature study is Ali. Research sample is equal to 35 systems and it is equal to statistical community members and include, all information systems that offering banking services to customers. Index test questionnaires using multiple regression analysis, the state of banks has been carried out. Statistical analysis tools are including Pearson correlation coefficient and beta. The findings of this study indicate that the main reason for the failure of most information systems in banks, are issues and problems from the management factor and operating components of the strategy, expectations and complexity.
 

Keywords

  1. اخوان، مریم؛ محمدلو، مسلم‌علی؛ و حبیبی، جعفر؛ (1383)، علل حیاتی موفقیت و شکست پروژه‌های فناوری اطلاعات در کشور، فصلنامه‌ی مطالعات صنعتی، شماره‌ی 6، دانشگاه علامه طباطبایی.
  2. لاودن، کنث و جین (1388)، سیستم‌های اطلاعات مدیریت، (ترجمه حبیب رودساز، سینا محمدنبی و امیرحسین بهروز)، تهران: دانشگاه علامه طباطبایی، چاپ اول.
  3. کلارک، استیو؛ (1382)، مدیریت استراتژیک سیستم‏های اطلاعاتی، (ترجمه سید محمد اعرابی و داوود ایزدی)، دفتر پژوهش‏های فرهنگی.
    1. AlSharif, M., Walter, P.B., & Turkey, A., (2004, April). Assessing the complexity of software architecture. In Proceedings of the 42nd Annual Southeast Regional Conference (pp. 98-103).
    2. Alter, S. (1999, March). A general, yet useful theory of information systems. Communications of AIS, 1(13), 1-70.
    3. Avison, D., & Fitzgerald, G. (2003). Information systems development: Methodologies, techniques and tools (3rd Ed.). Berkshire: McGraw-Hill.
    4. Baccarini, D.(1996,August). The concept of project complexity: A review. International Journal of Project Management, 14(4), 201-204.
    5. Barki, H., Rivard, S., & Talbot, J. (1993). Toward an assessment of software development risk. Journal of Management Information Systems, 10(2), 203-225.
    6. Braa,J. & Hedberg, C. (2000). Developing district-based health care information systems. In Proceedings of the IFIP WG9.4 Conference 2000, Cape Town, South Africa. Information flows, local improvisations, and work practices(pp. 113-128).
    7. British Computer Society (2003, April). The challenges of complex IT projects (Report). The Royal Academy of Engineering.
    8. Cole, A. (1997). Runaway projects - Cause and effects. Software word, 26(3), 3-5.
    9. Cash, C.H., & Fox, R. (1992). Elements of successful project management. Journal of Systems Management, 43(9), 10-12.
    10. DeLone,W.H.,&McLean,E.R.(2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4).
    11. Dix,A.,Finaly,J.,Abword,D,.&Beale,R.(2004). Human-computer interaction (3rd. Ed.). Harlow,UK: Pearson Education Limited.
    12. Garrity, E.J., & Sanders,L.G. (1998). Information systems success measurement. Hershey,PA: Idea Group Publishing.
    13. Glass,R. (1999) Evolving a new Theory of Project Success: Communications of the ACM, 41(7) November.
    14. Heeks,R.(2000). Failure,success,and improvisation of information systems projects in developing countrrie (Development Informatics Working Paper Series, Paper No. 11). Institute for Development Policy and Management, University of Manchester, UK. Retrieved April 1,2005, from standishgroup.com/ sample-research/chaose-1994-2.php
    15. Heeks, R. (2003). E-government for development success and failure rates of e-government in developing/transitional countries: Overview. E-Government for Development Information Exchange IDPM, University of Manchester,UK. Retrieved April 8,2005, from
    16. http://www.egov4dev.org/sfoverview.htm
    17. Irani, Z., Sharif, A.M., & Love, P.E.D. (2001). Transforming failure into success through organizational learning: An analysis of a manufacturing information system. European Journal of Information Systems, 10, 55-66.
    18. IT Cortex (2005). Failure rate, Statistics over IT projects failure rate. Retrieved April 10, 2005, from http://www.it-cortex.com/Stat-FailureRate.htm
    19. Jiang,J and Klein,G. (1999). Risks to different aspects of system success. Information & Management, 36 (5),263-271.
    20. Ketchell,M. (2003,Februrary 28). RMIT to scrap $47m software system. The Age. Retrieved 23 April,2004,from
    21. http://www.theage.com.au/articles/2003/02/27/1046064164879.html
    22. Kitiyadisai,K.(2000). The implementation of IT in reengineering the Thai revenue department. In Proceedings of the IFIP WG9.4 Conference 2000, Cape Town, South Africa. Information flows, local improvisations, and work practices.
    23. Koenig, M. (2003). Knowledge management, user education and librarianship. Library Review, 52(1-2), 10-17.
    24. Law, W.K., & Perez, K. (2005). Cross-cultural implementation of information systems. Journal of Cases on Information Technology, 7(2), 121-130.
    25. Liebowits,J. (1999). Information systems: Success or failure? Journal of Computer Information Systems. 40(1), 17-27.
    26. Lyytinen, K. and R. Hirschheim (1987). Information systems failures: a survey and classification of the empirical literature. In Oxford surveys in Information Technology. Vol. 4. Oxford University, Press, pp. 257-309.
    27. Montealegre, R., & Keil, M. (2000). De-escalating information technology projects: lessons from the Denver International Airport. MIS Quarterly, 24(3), 417-447.
    28. Nauman,A and Aziz,R and Ishagh,A.F.M. (2009). Information System Development Failure and Complexity: A Case Study. 251-252.
    29. Oz, E., & Sosik, J.J. (2000). Why information systems projects are abandoned: A leadershop and communication theory and exploratory study. Journal of Computer Information Systems, 41(1), 66-78.
    30. Sauer, C. (1993). Why information systems fail: Acase study approach. Oxfordshire,UK: Alfred Waller Ltd., Publishers.
    31. 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-37.
    32. Seddon, P. B., Staples, S., Patnayakuni, R., & Bowtell, M. (1999). Dimensions of information systems success. Communications of AIS, 2(3), 2-24.
    33. Standish Group (1994). The CHAOS report 1994. Retrieved November 30,2006, from http://www.standishgroup.com/sample-research/chaos-1994-1.php
    34. Standish Group (1999). Project resolution: The 5-year view. Retrieved November 30, 2006, from
    35. http://www.standishgroup.com/sample-research/PDFpages/chaos 1999.pdf
    36. Standish Group (2001). Extreme chaos. Retrieved November 30,2006, from http://www.standishgroup.com/sample-research/PDFpages/extreme-chaos.pdf
    37. Taylor,P. (2000). IT projects: Sink or swim. Computer Bulletin. 42(1), 24-26.
    38. Vandersluis, C (1997). Plan is key to avoiding IT project failures. Computing Canada, 23(9), 20.
    39. Wilson, M., & Howcroft, D. (2002). Reconstructing failure: Social shaping meets IS research. European Journal of Information Systems, 11(4), 236.