DOI QR코드

DOI QR Code

정보시스템 개발에 필요한 비즈니스 분석 역량 연구: IPA 기법을 활용하여

A Study of Business Analysis Competencies for Information Systems Development: Using IPA Techniques

  • 투고 : 2018.07.20
  • 심사 : 2018.08.21
  • 발행 : 2018.09.30

초록

최근 비즈니스의 경쟁 우위를 확보하기 위한 정보시스템 프로젝트의 성공 여부가 많은 이해관계자들에게 매우 중요해지고 있다. 정보시스템 프로젝트 성공에 관심을 갖는 주요 이해관계자는 일반적으로 시스템이 필요한 사용자, 이를 구축하는 개발자, 그리고 정보시스템 프로젝트 성공을 책임지는 관리자가 있다. 그런데, 최근 이러한 이해관계자들 간의 가교 역할을 수행하는 비즈니스 분석가의 필요성이 늘어나고 있다. 하지만 정보시스템 프로젝트 관리자와 개발자와 관련한 역량에 대한 연구는 많이 진행된 반면, 최근 늘어나고 있는 비즈니스 분석가의 역량에 대한 연구는 많이 진행되지 않고 있다. 본 연구는 정보시스템 프로젝트에 투입되는 비즈니스 분석가에게 필요한 역량은 무엇이고, 비즈니스 분석가에 대한 이해관계자들의 기대치와 만족도의 수준과 그 차이를 연구하고, IPA 기법을 활용하여, 비즈니스 분석가들이 집중적으로 개발해야 할 역량과 그렇지 않은 역량이 무엇인지를 조사하는 것이다. 본 연구 결과는 최근 정보시스템 프로젝트에 투입되는 비즈니스 분석가들에 대한 채용, 평가 및 교육에 필요한 역량 모델 또는 교육 프로그램 개발에 기초적인 정보를 제공하는데 큰 기여를 할 수 있을 것으로 확신한다.

In recent years, success of information system projects to possess competitive advantage in business has become very important for stakeholders. Stakeholders who are interested in the success of information system projects typically consist of users who need the system, developers who build it, and project managers who are responsible for project success. However, recently, there has been increasing in the number of business analysts engaged in bridging relationships among these stakeholders in information system projects. So far, there have been many researches on the competence of users, developers or project managers. But, the research on the competencies of business analysts has not been done much. So, in this study, what competencies are needed for business analysts who are engaged in information system projects are researched, and the level and difference of stakeholders' expectations and satisfaction with them are identified, using IPA techniques. The results of this study are expected to contribute greatly to providing basic information on the development of competency models or training programs needed for recruitment, evaluation and training of business analysts who are or will be engaged in information system projects.

키워드

참고문헌

  1. 김기윤, 나관식, 양동구, "요구사항 불확실성, 통제 표준화, 상호작용이 소프트웨어 품질에 미치는 영향", Asia Pacific Journal of Information Systems, 제12권, 제4호, 2002, pp. 101-120.
  2. 김현주, "역량기반인적자원관리(CBHRM) 의 도입과 발전: 한국 기업을 위한 상황론적 접근법", POSRI 경영경제연구, 제3권, 제1호, 2003, pp. 120-158.
  3. 전영욱, 김진모, "기업체 인적자원개발 담당자의 핵심직무역량모델 개발", 농업교육과 인적자원개발, 제37권, 제2호, 2005, pp. 111-137.
  4. 조숙진, 이석준, 함유근, "정보시스템 프로젝트의 위험요인에 관한 실증 연구", Asia Pacific Journal of Information Systems, 제16권, 제3호, 2006, pp. 143-158.
  5. 최장호, 곽찬희, 이희석, "IT 프로젝트 위험요인 식별 및 분석 프레임워크 연구", Information Systems Review, 제19권, 제4호, 2017, pp. 87-110.
  6. 홍영식, 김상덕, 오창규, "정보시스템 도입에 따른 변화관리 사례 연구: 대법원 변화관리 프로젝트를 중심으로", Information Systems Review, 제8권, 제3호, 2006, pp. 1-20.
  7. Abran, A. and P. Bourque, SWEBOK: Guide to the Software Engineering Body of Knowledge, IEEE Computer Society, Angela Burgess, Los Alamitos, CA, 2004.
  8. Ahmed, F., L. F. Capretz, S. Bouktif, and P. Campbell, "Soft skills and software development: A reflection from the software industry", International Journal of Information Processing and Management, Vol.4, No.3, 2013, pp. 171-191.
  9. Alami, A., "Do we really know what the 'analyst' in the 'business analyst' means?", 2015, Available at https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/3359/Do-we-really-knowwhat-the-Analyst-in-the-Business-Analyst-means.aspx
  10. Alami, A., "Sr. Business Analyst", 2015, Available at http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/3359/Do-we-really-knowwhat-the-Analyst-in-the-Business-Analyst-means.aspx-sthash.fFhaOexi.9BF3kexg.dpuf.
  11. Baartman, L. K. J. and E. de Bruijn, "Integrating knowledge, skills and attitudes: Conceptualising learning processes towards vocational competence", Educational Research Review, Vol.6, No.2, 2011, pp. 125-134.
  12. Baccarini, D. and A. Collins, "Critical success factors for projects", Environment, Proceedings of the 17th ANZAM Conference, 2, 2003.
  13. Blais, S., Business Analysis: Best Practices for Success, John Wiley & Sons, Hoboken, NJ, 2011.
  14. Boyatzis, R. E., The Competent Manager: A Model for Effective Performance, John Wiley & Sons, Hoboken, NJ, 1982.
  15. Charette, R. N., "Why software fails", IEEE Spectrum, 2005, Vol.42, No.9, p. 36.
  16. Clancy, T., The CHAOS Report, The Standish Group International, Inc., 1995.
  17. Cooke, J. L., The Power of the Agile Business Analyst: 30 Surprising Ways a Business Analyst Can Add Value to Your Agile Development Team, IT Governance Publishing, 2013.
  18. Damian, D., S. Marczak, and I. Kwan, "Collaboration Patterns and the Impact of Distance on Awareness in Requirements-Centred Social Networks", Requirements Engineering Conference, RE'07. 15th IEEE International, IEEE, 2007.
  19. Davis, B., Managing Business Analysis Services: A Framework for Sustainable Projects And Corporate Strategy Success, J. Ross Publishing, Plantation, FL, 2013
  20. Debra Paul, D. Y. A. J. C., Business Analysis (2ed.), British Computer Society, Swindon, UK, 2014.
  21. Hager, P. and A. Gonczi, "What is competence?", Medical Teacher, Vol.18, No.1, 1996, pp. 15-18.
  22. Hass, K. B., Lori lindbergh, Richard Vander Horst, and Kimi Ziemski, from Analyst to Leader: Elevating the Role of the Business Analyst, Management Concepts, Vienna, VA, 2008.
  23. Hoffmann, T., "The meanings of competency", Journal of European Industrial Training, Vol.23, No.6, 1999, pp. 275-286.
  24. IIBA, "Annual Report", International Institute of Business Analysis, Oakville, Canada, 2016.
  25. IIBA, "IIBA business analysis competency model, version 3.0", International Institute of Business Analysis, Oakville, Canada, 2011.
  26. IIBA, A Guide to Business Analysis Body of Knowledge (BABOK), version 3, International Institute of Business Analysis, Oakville, Canada, 2014.
  27. Jacobs, R., "Getting the measure of management competence", Personnel Management, Vol.21, No.6, 1989, pp. 32-37.
  28. Jiang, J. J., G. Klein, C. V. Slyke, and P. Cheney, "A note on interpersonal and communication skills for IS professionals: Evidence of positive influence", Decision Sciences, Vol.34, No.4, 2003, pp. 799-812.
  29. Jonasson, H., Determining Project Requirements (2ed.), Auerbach Publications, New York, NY, 2012.
  30. Jonson, J., J. Crear, R. Kelley, L. Gesmer, and J. Poort, The CHAOS Report, The Standish Group International, Inc., 2015.
  31. Kirk, M., E. Tonkin, and H. Skirton, "An iterative consensus-building approach to revising a genetics/genomics competency framework for nurse education in the UK", Journal of Advanced Nursing, Vol.70, No.2, 2014, pp. 405-420.
  32. Lavazza, L., "Business goals, user needs, and requirements: A problem frame-based view", Expert Systems, Vol.30, No.3, 2013, pp. 215-232.
  33. Li, Y., M. H. Yang, G. Klein, and H. G. Chen, "The role of team problem solving competency in information system development projects", International Journal of Project Management, Vol.29, No.7, 2011, pp. 911-922.
  34. Maiden, N., "User Requirements and System Requirements", IEEE Software, Vol.25, No.2, 2008, pp. 90-91.
  35. Martilla, J. A. and J. C. James, "Importance-performance analysis", The Journal of Marketing, Vol.47, No.1, 1977, pp. 77-79.
  36. Mcclelland, D. C., "Testing for competence rather than for "intelligence"", Am Psychol, Vol.28, No.1, 1973, pp. 1-14.
  37. Oliver, R. L., "A cognitive model of the antecedents and consequences of satisfaction decisions", Journal of Marketing Research, Vol.17, No.4, 1980, pp. 460-469.
  38. Oxford University Press, "Competence", 2016, Available at http://www.oxforddictionaries.com/definition/english/competence?q=COMPETENCY.
  39. Park, J. and S. R. Jeong, "A Study on the Relative Importance of Underlying Competencies of Business Analysts", KSII Transactions on Internet and Information Systems, Vol.10, No.8, 2016, pp. 3986-4007.
  40. Quigley, R. T., An Analysis of Underlying Competencies and Computer and Information Technology Learning Objectives for Business Analysis (Theses and Dissertations), Purdue University Purdue e-Pubs, 2013.
  41. Robertson, S. and J. Robertson, Mastering the requirements process: Getting requirements right, Addison-Wesley, Boston, MA, 2012.
  42. Rothwell, W. J. and H. C. Kazanas, Mastering the Instructional Design Process: A Systematic Approach (4ed.), John Wiley & Sons, Hoboken, NJ, 2014.
  43. Rubens, J., "Business analysis and requirements engineering: The same, only different?", Requirements Engineering, Vol.12, No.2, 2007, pp. 121-123.
  44. Shukla, V., D. Pandey, and R. Shree, "Requirements engineering: A survey", Requirements Engineering, Vol.3, No.5, 2015, pp. 28-38.
  45. Sonteya, T. and L. F. Seyrnour, "Towards an understanding of the business process analyst: An analysis of competencies", Journal of Information Technology, Vol.11, 2012, pp. 43-63.
  46. Sparrow, P., "Too good to be true?", People Management, Vol.2, No.24, 1996, pp. 22-27.
  47. Spencer, L. M. and P. S. M. Spencer, Competence at Work Models for Superior Performance, John Wiley & Sons, Hoboken, NJ, 1993.
  48. Verner, J., K. Cox, S. Bleistein, and N. Cerpa, "Requirements engineering and software project success: An industrial survey in Australia and the US", Australasian Journal of Information Systems, Vol.13, No.1, 2005.
  49. Vickers, A., "Satisfying Business Problems", Software IEEE, Vol.24, No.3, 2007, pp. 18-20.
  50. Wiegers, K., Software Requirements (3rd ed.), Microsoft Press, Redmond, WA, 2013.