정보시스템 프로젝트의 위험요인에 관한 실증 연구

목차 (Table of Contents)

• I. 서론
• II. 문헌 연구
• III. 연구 방법
• 3.1 위험요인 리스트 도출
• 3.2 설문조사 및 데이터 수집
• IV. 데이터 분석 결과
• 4.1 표본의 기술
• 4.2 데이터 분석
• 4.3 위험요인 우선순위
• 4.4 프로젝트 관리자와 프로젝트 수행자간 위험요인별 인식도 비교분석
• V. 연구 결론
• 참고문헌

참고문헌 (Reference)

1 쌍용정보통신, "투자효과분석 및 정보시스템 평가 방법론 개발" 1999.

2 이석준, "정보시스템 프로젝트의 성과영역별 위험요인에 관한 탐색적 연구" 11 (11): 2004

3 채서일, "사회과학조사방법론" 학현사 2003.

4 Barki,H, "Toward an Assessment of Software Development Risk" 10 (10): 203-225, 1993

5 Haimes,Y.Y, "Total Risk Management" 11 (11): 69-171, 1991

6 The Standish Group International,, "The Standish Report" The Standish Group International, Inc. 2001.

7 Remenyi, D.,, "The Effective Measurement and Management of IT Costs and Benefits" Butterworth-Heinemann 2000.

8 The Standish Group International,, "The Chaos Report" The Standish Group International, Inc. 1995.

9 Higuera,R.P, "Team Risk Management" January1995.

10 Mckeen,J.D, "Successful Strategies for User Participation in Systems Development" 14 (14): 133-150, 1997

11 Davis,G, "Strategies for Information Requirements Determination" 21 (21): 4-30, 1982

12 Gibbs,W.W, "Software’s Chronic Crisis" 271 (271): 86-95, 1994

13 Deephouse,C, "Software Process and Project Performance" 12 (12): 187-205, 1995

14 Keil,M, "Pulling the Plug: Software Project Management and the Problem of Project Management and the Problem of Project Escalation" 19 (19): 421-447, 1995

15 Hartman,Francis, "Project Management in the Information Systems and Information Technologies Industries" 5-15, sep.2002

16 Burke,R, "Project Management Planning and Control Techniques" Burke Publishing 2004.

17 McFarlan,F.W, "Portfolio Approach to Information Systems" 59 (59): 142-150, 1981

18 Martlin,J. Shio, "New Look at MIS" 1977.05

19 Bell,T.E, "Managing Murphy;s Law: Engineering a Minimum-Risk System" 26 (26): 24-27, 1989

20 Wideman,R.M, "Management" 17 (17): 20-26, 1986

21 Lederer,A.L, "Key Prescriptions for Strategic Information Systems Planning" 1 (1): 35-62, 1996

22 Turban, E.,, "Information Technology for Management" 563-564, 2002

23 Nord,G.D, "Information Systems Project Development: Knowledge and Domain Requirements for the Systems Analyst" 17-24, 1997

24 Zmud,R.W, "Individual Differences and MIS Success: A Review of the Empirical Literature" 25 (25): 966-979, 1979

25 Lucas,H.C, "Implementation: The Key to Successful Information Systems" New York: Columbia University Press 1981.

26 Alter,S, "Implementation Risk Analysis" 13 (13): 103-119, 1979

27 Schmidt,R, "Identifying Software Project Risks: An International Delphi Study" 17 (17): 5-36, 2001

28 Mckeen,J.D, "How does Information Technology Affect Business Value? A Reassessment and Research Propositions" 10 (10): 229-240, 1993

29 Moynihan,T, "How Experienced Project Managers Assess Risk" 14 (14): 35-41, 1997

30 Grafton, Whyte, "Factors Affecting Information Systems Success" 7 (7): 74-93, 1996

31 The Standish Group International, "Extreme Chaos" The Standish Group International, Inc. 2000.

32 Leonard-Barton,D, "Developer-User Interaction and User Satisfaction in Internal Technology Transfer" 36 (36): 1125-1139, 1993

33 Hofstede,G, "Cultures and Organizations: Software of the Mind" Mcgraw-Hill 1991.

34 Applegate,L.M, "Corporate Information Systems Management: Text & Cases, 5/ed" Mcgraw-Hill 1999.

35 Clark, B.,, "COCOMO II Post-Architecture Model" 20 : 477-481, 1998

36 Barki, H.,, "An Integrative Contingency Model of Software Project Risk Management" 17 (17): 37-69, 2001

37 Jiang,James J, "A Measure of Software Development Risk" 33 (33): 30-41, 2002

38 Project Management Institute, "A Guide to the Project Management Body of Knowledge" Project Management Institute, Inc 2000.

39 Nidumolu,S, "A Comparison of the Structural Contingency and Risk-Based Perspectives on Coordination and Software Development Projects" 13 (13): 77-113, 1996

40 Hilliam, C.E., "A Case Study Approach to Evaluation of Information Technology/Information Systems Investment Evaluation Processes Within SMEs" 4 : 0-, 2000