台灣中小型軟體發展組織如何實施CMMI Level 2

Implementing the CMMI Level 2 for Small and Medium Software Development Organization in Taiwan

黃端祥(Duan-Hsiang Huang)

指導教授 ： 劉士豪

中原大學/商學院/資訊管理研究所/碩士(2004年)

https://doi.org/10.6840/cycu200400699

摘要

隨著全球化的趨勢，無論是個人、企業，乃至於國家，都積極的在努力想辦法提昇競爭力，而資訊科技的運用，實為決勝的關鍵。但是資訊系統建置也因為各種內在外在的環境因去而變成非常的困難。即使在美國也只有32%的資訊系統建置專案可以順利結案，國內更是不言可喻。
國內軟體業者多半是屬於中小型的企業，礙於成本或其他的考量，並沒有嚴謹的工程方法，導致專案結案率偏低，甚至有所謂的非技術結案的傳聞。而CMMI(Capability Maturity Model - Integrated,能力成熟度整合模式)是一個可以改進系統工程和軟體工程的整合模式，它因美國國防部於1997年10月下令SEI停止對CMM的研究，轉而致力於開發CMMI，幫助企業解決使用多個CMM的問題。SEI也宣佈CMMI產品將取代CMM，所以在2000年8月11日頒布CMMI-SE/SW 1.0版本，2001年12月發行1.1版本，並預計於2003年完成從CMM到CMMI的過渡。資策會也在經濟部的贊助下，自SEI技術引進CMMI，集合人力翻譯了下列文件：
CMMISM for System Engineer/Software Engineering/Integrated Product and Process Development, Version 1.02 (CMMISM-SE/SW/IPPD V1.02), Staged Represetation, CMU/SEI-2000-TR-030。並於2002年6月出版，以方便有心追求軟體品質的國內人士，迅速了解及引用。
綜觀自1992年迄今，全球許多不同組織以一個或多個CMMs為協助企業作全面性的流程改善及整合活動的效益，並通過CMM第二級到第五級認證者多達七百餘家，除了肯定其軟體成熟度外，更象徵著其具有跨足國際市場的能力。
在這七百餘家企業當中，美國、印度廠商最多，中國大陸亦有不同等級的通過家數，而我國至目前為止，僅有四家通過CMMI Level 2。在此CMM轉換為CMMI之際，直接導入CMMI技術，正是迎頭趕上的契機。但是導入CMMI是所費不菲的工作。在花費上，單以評鑑(Appraisal)作業對台灣中小型的軟體發展組織而言，就是一項非常大的開支，而在整個導入過程上，也需要一段相當的時間、專職的人力、工具以及其他資源的投入。
本研究透過幾個CMMI實際的多重個案研究，在透過中小型的軟體發展組織與大型軟體發展組織比較分析中，以及經驗的分享，可以為中小型的軟體發展組織找到一個提昇軟體發展能力的捷徑，不用花太多的成本，也不用走太多的冤枉路。

關鍵字

CMM ； CMMI ； 軟體工程 ； 軟體發展

並列摘要

Improved competition is the most important goal for a person, a company, and a county after globalization. The key of success to improve competition is how to use information technology. However, under the current circumstance, it is a very difficult task to build up an information system. In the U.S., only 32% of the information system projects can be done and in Taiwan, much less than 32% of the projects can be completed.

In Taiwan, most of the software companies are rather small or middle. Because of the matter of the cost, they did not follow engineer process. Therefore, the ratio of projects’ completions is lower. Most of them did not completed. The solution to help a team to complete their project is CMMI, Capability Maturity Model Integrated. CMMI is a way to improve integration of the system engineer and the software engineer. It started on Oct, 1997 when the SEI, Software Engineering Institute, followed the order of The U.S. military, stopped the CMM research project. The CMMI help business companies solved the problem of using CMMs. After that, SEI announced version 1.0 of the CMMI-SE/SW, the successor of CMM, at Aug 11, 2000. Also, SEI has also announced version 1.1 on Dec, 2001. SEI has planed to finish transformation from CMM to CMMI in 2003. In Taiwan, Institute for Information Industry, supported by 經濟部, has sourced CMMI from SEI and has translated the following documents in to traditional Chinese:

CMMISM for System Engineer/Software Engineering/Integrated Product and Process Development, Version 1.02 (CMMISM-SE/SW/IPPD V1.02), Staged Representation, CMU/SEI-2000-TR-030. It has been published on Jun 2002 for people who want to know and made good quality software.

Since 1992, many organizations gave business companies an assist with CMMs to improve their software processes and emphasize the effect of system integration. More than 700 companies have been validated the appraisal of CMM level II to level V.

In these 700 companies, most of them are from the U.S. and India. In China, some of companies have passed the appraisal. In Taiwan, up to now, there are only four passing the appraisal of CMM level II. Meanwhile, leading in CMMI technology is great opportunity to catch up the others. However, it would be a huge expense. For example, “Appraisal” will cost a lot overall. Also, it needs a lot of time, people, and resources to get involved in whole process.

This research based on several CMMI Mini-Cases. Through these cases, we can cost done and improve software development for small or middle software organization.

並列關鍵字

Software Development ； CMMI ； CMM ； Software Engineering

參考文獻

3. Software Engineering Institute (SEI) at Carnegie Mellon University(CMU)，Concept of Operations for the CMMISM，January 15, 2001

7. SEI，The Personal Software Process (PSP)，CMU/SEI-2000-TR-022，2000

8. The Team Software Process (TSP)，CMU/SEI-2000-TR-023，2000

24. 鄭秀華，影響系統整合專案委外績效之因素（以知識管理與軟體能力成熟度整合模式之觀點）， 2003

附錄B：參考文獻