Responsive image
博碩士論文 etd-0708107-124517 詳細資訊
Title page for etd-0708107-124517
論文名稱
Title
CMMI調適架構之研究:以風險管理為例
A study on the CMMI tailoring process: the case of risk management
系所名稱
Department
畢業學年期
Year, semester
語文別
Language
學位類別
Degree
頁數
Number of pages
105
研究生
Author
指導教授
Advisor
召集委員
Convenor
口試委員
Advisory Committee
口試日期
Date of Exam
2007-07-03
繳交日期
Date of Submission
2007-07-08
關鍵字
Keywords
風險管理、軟體流程、CMMI調適準則
CMMI tailoring guides, risk management, software process
統計
Statistics
本論文已被瀏覽 5839 次,被下載 0
The thesis/dissertation has been browsed 5839 times, has been downloaded 0 times.
中文摘要
我國軟體業者與資訊服務業者正面臨全球化的競爭,但國內由於人才資源不足,且大多數業者缺乏軟體工程概念,因此軟體發展能力普遍落後國際水準。除此之外,國內軟體產值較低,且內需市場太小,廠商一起搶食市場,導致獲利不易。近年來,由於SEI陸續推出多種組合版本的整合能力成熟度模型,故本研究蒐集及探討軟體產業導入CMMI之相關理論架構,以軟體專案風險流程管理為例,建立不同專案規模之流程調適架構及原則。
針對風險管理流程,本研究依CMMI LEVEL 3各項實行流程定義出調適構面,並採個案訪談方式深入探討個案公司八項計畫,透過分析、歸納、及整理其可能之調適原則。其研究結果綜整如下:
一、建立風險管理策略
(一)撰寫風險計畫,內容包括風險界定、分析、降低、處理、及監測等各項活動。
(二)提供活動的實施方法、判斷準則、執行門檻、處理程序或使用工具。
(三)產生必要之工作產品(例如:資料、紀錄、文件等)。
(四)制訂風險監測或再評估之時間間隔(至少每月一次)。
二、建立各項流程調適原則
(一)可視專案特性准允調整與修正。
(二)設計與執行需要有回饋機制。
(三)需要具體執行方法,無法完全依賴制度。
最後,本研究模式與架構未來將可推廣於SEI後續發展之新模式或其他大型國際標準,以做為各型軟體組織在進行軟體流程改善之參考。
Abstract
The software industry and the information service providers in Taiwan are facing global competition but generally falling behind the international level for their software development ability due to short of capable manpower and lack of software engineering concept. Moreover, the domestic output value of software is relatively low and the domestic market is also too small; companies are struggling for the market and making profit has become difficult. To solve this issue the Software Engineering Institute (SEI) has developed several combinations of the Capability Maturity Model Integrated (CMMI) in recent years. In this study, theories of implementing CMMI in the software industry are discussed. Taking risk management for a software project as example, we have established the structure and guides of process tailoring for projects of various scales.
On the process of risk management, we firstly defined the tailoring aspects according to the CMMI Level 3 implement process, and then interviewed the case study company for their eight plans to analyze and induce the possible tailoring guides. Our findings are as follows.
1. Establishing the risk management strategy
(1) Making a risk plan, including activities such as risk definition, analysis, reduction, treatment and monitoring.
(2) Providing implement methods, judgment rules, execution thresholds, treatment process, or tools for those activities.
(3) Producing necessary output, such as data, records, and documents.
(4) Setting up timeframe for risk monitoring or re-evaluation, at least once a month.
2. Establishing the tailoring guides for the process
(1) Adjustment and change are allowed, depending on the project property.
(2) Feedback is necessary for design and implementation.
(3) Concrete and practical methods are necessary; the system is not fully reliable.
The research model and structure of this study can be further applied to the newly developed SEI models or other large-scale international standards in the future as a reference for the software organizations to improve their software process.
目次 Table of Contents
論文提要 I
論文審定書 II
摘要 III
Abstract IV
致謝詞 V
目錄 VI
圖目錄 VIII
表目錄 IX
第一章、緒論 1
第一節、研究背景 1
第二節、研究動機 1
第三節、研究目的 3
第四節、研究流程 4
第二章、文獻探討 5
第一節、軟體產業的介紹與特性 5
第二節、CMMI介紹、導入與各流程 14
第三節、CMMI對軟體產業的之重要性 23
第四節、軟體流程與軟體流程改善 28
第五節、CMMI調適準則 29
第六節、軟體風險管理 33
第三章、研究方法 42
第一節、個案研究法 42
第二節、研究架構 50
第三節、研究對象 51
第四節、研究工具 52
第五節、資料蒐集方法 53
第六節、研究限制 53
第四章、個案分析與討論 55
第一節、大型計畫 55
第二節、小型計畫 68
第五章、研究結果 76
第一節、跨組個案風險比較 76
第二節、跨組個案調適構面比較 80
第三節、跨組個案流程領域比較 83
第六章、結論與建議 84
第一節、結論 84
第二節、建議 85
參考文獻 87
附錄 93
參考文獻 References
1.王文科(1999),教育研究法,臺北市 : 五南,第五版。
2.白錦門(1994),個案法之研究,教育研究方法論文集,台北市:台灣書店。
3.行政院主計處(2003),民國九十年台閩地區工商及服務業普查調查報告。
4.何英煒(2002,July),軟體認證商機 中外廠商擬聯手搶食, 工商時報(台北)。
5.周祥東(2002),「專案風險管理」,風險管理學報,第11 期,第43-65 頁。
6.林大舜、張啟昌(2003),「建構資訊推動計劃風險管理模式之研究」,管理與系統,第十卷,第三章,第303-328 頁。
7.林永裔(2001),「應用模糊理論在大型軟體專案」,逢甲大學工業工程系碩士論文。
8.林輝耀(1996),「軟體專案風險評估模式的架構」,企業管理學報,第39 期,第37-52 頁。
9.胡幼慧主編(1996),「質性研究:理論、方法及本土女性研究實例」,台北:巨流。
10.胡佑長(2001,October),「軟體能力成熟度CMM評鑑機制與架構簡介」,軟體產業通信,第四十一期。
11.胡暐珊譯(2002),Richard Murch 著,專案管理最佳實務,藍京出版社,台北。
12.許光華、何文榮(1998),專案管理-理論與實務,華泰書局,台北。
13.軟體產業通訊(2001,September),提升國內軟體產業國際競爭力 資策會將引進軟體CMM 技術,軟體產業通訊第40 期。
14.陳建名(1995),「軟體專案之風險分析」,中山大學資管所碩士論文,高雄。
15.陳相亨(1999),以組織文化的觀點來探討全面品管對軟體程序成熟度的影響,國立中正大學資訊管理研究所未出版之碩士論文。
16.陳燿昇(1998),組織特性、資訊化成熟度、資訊部門特性與企業軟體程序成熟度關係的探討,國立中正大學資訊管理研究所未出版之碩士論文。
17.陳繼堯(1999),「我國風險管理的回顧與將來」,風險管理季刊,第二期,第9-14 頁。
18.黃仁伯 楊千(1997,October),「中小型軟體公司之規範式軟體程序模式建構」,交大管理學報,Vol.17, No.3, p.125-145
19.經濟部中小企業處(2004),民國九十二年中小企業白皮書。
20.經濟部技術處(2000,November),能力成熟度整合模式CMMI-SE/SW/IPPD V1.02.
21.經濟部技術處(2002), CMMI導入指引 V1.0(第二級).
22.經濟部技術處(2004),資訊服務產業年鑑。
23.葉重新(2001),教育研究法初版,台北市:心理。
24.葉蘇蓉(1999),「建立軟體專案風險衡量模式之研究-加入組織慣性變項」,暨南大學資管所碩士論文,南投。
25.蔡逢裕(2002),「軟體開發之風險評估系統」,中正大學資管所碩士論文。
26.鄧家駒(1999),風險管理,華泰書局,台北。
27.謝國棟(1995),臺灣地區大型企業資訊部門軟體程序成熟度及其相關因素之探討,國立中正大學資訊管理研究所未出版之碩士論文。
28.財團法人資訊工業策進會,http://www.iii.org.tw/
29.Addison, T.,(2003).“E-commerce project development risks: evidence from a Delphi survey”, International Journal of Information Management, 23, 25-40.
30.Armisted, C., (1984)“How Useful are Case Studies”, Training and Development Journal, Vol. 38, pp. 75-77.
31.Barki, H., S. Rivard, and J. Talbot,(1993).“To-ware an assessment of software development risk”, Journal of Information Systems, Fall, 203-225 .
32.Batista, J. and Figueiredo, A. D.(2000). “SPI in a Very Small Team: a Case with CMM”, Software Process-Improvement and Practice, 5, 243-250
33.Billings, C., Clifton, J., Kolkhorst, B., Lee, E., and Wingert, W. (1994). “Journey to a Mature Software Process, ”,IBM System Journey,33.
34.Boehm, B. W.,(1991).“Software Risk Management: Principles and Practices”, IEEE Software, January, 32-41.
35.Boehm, B. W.,(2000).“Software Cost Estimation with COCOM II”, Prentice Hall, PTR.
36.Byrnes Paul , Phillips Mike (1996, April). “Software Capability Evaluation Version 3.0 : Method Description(CMU/SEI-96-TR-002)”. Software Engineering Institute.
37.CMMI Product Development Team. (2001,December). “CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development, Version 1.1 Staged Representation, ” CMU/SEI-2002-TR-004, Carnegie Mellon University Software Engineering Institute, Pittsburgh, Pennsylvania, U.S.A.
38.ComponentSoftware Inc. (2002-2004) ComponentSoftware RCS Pro, Version 3.0.
39.Dedrick, J, & Kraemer, L. K. (2000)“Asia's computer challenge”, New York: International Creative Management.
40.Detlev J. Hoch,Cyriac R. Roeding (2000)” Management Insights from 100 Software Firms around the World”,Secrets of Software Success.
41.Fairly, R.,(1994).“Risk management for software projects”, IEEE Software, 57-67.
42.Feagin, J. R., (1991)”A Case For the Case Study,” Chapel Hill: The University of North Carolina Press.
43.Fitzgerald, B. and O’Kane, T.(1999).“A Longitudinal Study of Software Process Improvement,” IEEE Software, May-Jun, 37-45
44.Greene, G.C., Caracelli, V.J., and Graham, W.F., (1989) “Towards a conceptual framework for mixed-method evaluation designs”, Educational evaluation and policy analysis, Vol. 11, No. 3, pp. 255-274.
45.Houston, D. X., G. T. Mackulak, and J. S. Collofello,(2000).“Stochastic simulation of factor potential effects for software development risk management”, The Journal of System and Software, 11(5), 247-257 .
46.Humphrey W.(1989). “Managing the Software Process,” Addison-Wesley
47.Jiang, J. J. and K. Gary,(2001).“Software Project Risks and Development Focus ”, Project Management Journal, 3(1), 4-9.
48.Jones, G. W.,(1990).“Software Engineering”, John Wiley and Sons Ltd., American.
49.Kautz, K.(1998). “Software Process Improvement In Very Small Enterprises: Does It Pay Off?,” Software Process-Improvement and Practice, 4, 209-226
50.Kelly, D.P. and Culleton, B.(1999). “Process Improvement for Small Organizations,” IEEE Software, Oct., 41-47
51.Knight, K. W.,(1999).“The Risk Management Process,” Risk Management Conference and Exhibition, 1-14.
52.Masters Steve, Bothwell Carol. (1995, February).”CMM Appraisal Framework, Version 1.0(CMU/SEI-95-TR-001).” Software Engineering Institute.
53.Matthew, L.,(1983).“Risk management Manual Volume I, California: Merrit Company,” U.S.A., 1-2.
54.Myerson, J.,(1999).“Risk Management,” International Journal of Network Management, 9, 305-308.
55.Olsen, T., Humphrey, W. and Kitson, D.(1989).“Conducting SEI-assisted software process assessment. Technical Report,”CMU/SEI-89-TR-7, Pittsburgh.
56.Paulk, M.C., Curtis, B., Chrissis, M. and Weber, C.(1993a).”Capability Maturity Model for Software, Version 1.1.,” Technical Report, CMU/SEI-93-TR-024, Pittsburgh.
57.Paulk, M.C., Weber, C., Garcia, S., Chrissis, M. and Bush, M. (1993b). “Key Practices of the Capability Maturity Model , Version 1.1.,” Technical Report, CMU/SEI-93-TR-025, Pittsburgh.
58.Pressman, R.S.(1992). “Software Engineering: A Practitioner's Approach”, 3rd edition, McGraw-Hill, New York.
59.Rainer, A. and Hall, T.(2003).”A Quantitative and Qualitative analysis of Factors Affecting Software Process,” The Journal of Systems and Software, 66, 7-21
60.Rakos, J. J.,(1990).“Software Project Management for Small to Medium Sized Projects”, Prentice-Hall, Inc., American.
61.Saiedian, H. and Chennupati, K.(1999). “Towards an evaluative framework for software process improvement models”, The Journal of Systems and Software, 47, 139-148
62.Strauss, A., and Corbin, J., (1990) “Basics of Qualitative Research-Grounded Theory Procedures and Techniques,” Sage Pulications.
63.Thomsett, R.,(1993).“Third wave project management: A handbook for managing the complex information systems for the 1990s”, Prentice Hall .
64.Ward, R.P., Fayad, M.E., and Laitinen, M.(2001). “Software Process Improvement in the Small,” Communication of the ACM, 44(4),105-107
65.Wilson, D.N., Hall, T. and Baddoo, N.(2001).”A framework for evaluation and predicton of software process improvement success,” The Journal of Systems and Software, 59, 135-142
66.Yin, R. K., (1993). “Applications of Case study research,” Newbury Park, CA: Sage.
電子全文 Fulltext
本電子全文僅授權使用者為學術研究之目的,進行個人非營利性質之檢索、閱讀、列印。請遵守中華民國著作權法之相關規定,切勿任意重製、散佈、改作、轉貼、播送,以免觸法。
論文使用權限 Thesis access permission:校內校外均不公開 not available
開放時間 Available:
校內 Campus:永不公開 not available
校外 Off-campus:永不公開 not available

您的 IP(校外) 位址是 3.88.60.5
論文開放下載的時間是 校外不公開

Your IP address is 3.88.60.5
This thesis will be available to you on Indicate off-campus access is not available.

紙本論文 Printed copies
紙本論文的公開資訊在102學年度以後相對較為完整。如果需要查詢101學年度以前的紙本論文公開資訊,請聯繫圖資處紙本論文服務櫃台。如有不便之處敬請見諒。
開放時間 available 已公開 available

QR Code