自美國軟體工程研究所(Software Engineering Institute, SEI)於2001年發表了軟體能力成熟度整合模式(Capability Maturity Model Integration, CMMI)以來，CMMI已成為全球普及的流程改善模式。SEI也於2005年公布了一份CMMI導入效益報告，包含了成本、時程、生產力、品質、客戶滿意度與投資報酬率等六個效益構面資訊，並顯示以CMMI為基礎之流程改善模式是可為組織帶來正面效益。然而CMMI流程改善是一種長期且持續的活動，流程改善導入時間對不同流程改善效益構面應有不同的影響。若能瞭解流程改善導入時間對不同流程改善效益構面影響的程度，對組織瞭解流程改善時間對效益構面應有許多的幫助，故本篇論文的主要目的在探討時間維度的變數對國內CMMI組織在導入時所收集之量化績效資料的影響。
首先，本研究針對國內41家導入CMMI組織進行成本、時程、品質、客戶滿意度、投資報酬率及員工等六個構面共22個效益指標及相關導入背景資訊之收集。根據所收集之效益資料，本研究再以流程改善時間為變數，利用TwoStep集群分析法進行分群，並以無母數統計方法加以檢定驗證，以瞭解在不同時間維度對量化效益的影響情形。研究結果發現，整體而言，隨著流程改善時間的增加，僅品質構面效益是有顯著的提升；至於就導入間隔時間長短而言，則對成本、時程、品質之部分指標有顯著的影響。透過本研究的成果，相信將可引導組織能更精確地投入資源於CMMI的導入上，進而使導入效益最大化。

Since Software Engineering Institute (SEI) released Capability Maturity Model Integration (CMMI) in 2001, CMMI has been worldwide adopted to help organizations evaluate and improve the development and maintenance processes of products and services, and to help acquirers improve the acquisition capabilities. According to SEI 2005 CMMI performance results of cost, schedule, productivity, quality, customer satisfaction and return on investment, it showed that CMMI-based software process improvement (SPI) can bring positive performance to adopters. However, CMMI-based SPI is a long-term and continuous activity, and the improvements of different performance categories may be influenced by the time of SPI activity. If we can know how the time dimension affects the CMMI-based SPI performance, we can then more effectively utilize resources in implementing CMMI-based SPI. Hence, the purpose of this research is to investigate the relationship between the time dimension and quantitative CMMI-based SPI performance.
In this study, we collected the 22 metrics of cost, schedule, personnel, quality, customer satisfaction and return on investment and related background information from 41 Taiwan CMMI-certified organizations. Based on these data, we adopted TwoStep clustering and non-parametric statistics to analyze the effects of the time dimension on the CMMI-based SPI performance. The results of this study showed that as the improvement time increases, only the metrics of the quality category have significant performance improvements. As for the time span between two introduced maturity levels, the time span is greater, the more significant effect on the metrics of cost, schedule and quality categories will be. The results of this study can help the CMMI adoption organizations know more about the CMMI-based SPI performance affected by the time allocated to SPI.

中文部分
[1] 吳宗穆，「軟體流程改善量化績效指標集制定之研究」，碩士論文，國立台灣科技大學，民國九十六年。
[2] 郭怡岑，「組織特性與投入資源對CMMI流程改善效益影響之研究」，國立台灣科技大學，民國九十五年。
[3] 李金泉，「精通SPSS 統計分析實務與應用」，全華圖書股份有限公司，民國九十六年。
[4] 吳明隆「SPSS操作與應用 變異數分析實務」，五南圖書出版股份有限公司，民國九十七年。
[5] 經濟部工業局提升資訊軟體品質(CMMI)計畫網站，http://www.cmmi-taiwan.org.tw/

英文部分
[6] Campbell, D. T., & Stanley, J. C. Experimental and Quasi-experimental Designs for Research. Chicago, IL: Rand McNally, 1966.
[7] Diane L. Gibson, Dennis R. Goldenson, Keith Kost, 2006. Performance Results of CMMI-Based Process Improvement. CMU/SEI-2006-TR-004.
[8] Dyba, T., Member, IEEE Computer Society. “An Empirical Invstigation of the Key Factors for Success in Software Process Improvement.“ IEEE Transaction on Software Engineering, Vol 31, NO.5, May 2005, pp. 410-424.
[9] Emam, K & Briand, L. (1997). Costs and benefits of software process improvement. Institute for Experimental Software Engineering (IESE) Report No 047.97/E.
[10] Goldenson, D.R. & Gibson, D.L. (2003). Demonstrating the impact and benefits of CMMI : an update and preliminary results. Special Report, CMU/SEI-2003-SR-009
[11] Harter,D.E. ,Laughter,S.A. “Quality Improvement and Infrastructure Activity Costs in Software Development: A Longitudinal Analysis.“ Management Science Vol. 49, No. 6, June 2003, pp. 784–800
[12] Herbsleb, J.; Carleton, A.; Rozum, J.; Siegel, J.; & Zubrow, D. (1994) Benefits of CMM-Based Software Process Improvement: Initial Results , CMU-SEI-94-TR-013, ADA 283848.
[13] Herbsleb, J., Goldenson, D.R. (1996). A systematic survey of CMM experience and results. 18th International Conference on Software Engineering (ICSE), 323-330
[14] Iversen, J.; Ngwenyama, O. “Problems in measuring effectiveness in software process improvement: Alongitudinal study of organizational change at Danske Data.“ Internation Journal of Information Management 26(2006) 30-43.
[15] Jiang, J.J., Klein, G. Hwang, H.G. Huang, J & Hung, S.Y. (2004). An exploration of the relationship between software development process maturity and project performance. Information & Management 41(3), 279-288.
[16] Krishnan, M.S. & Kellner, M. I. “Measuring Process Consistency: Implications for Reducing Software Defects.” IEEE Transactions on Software Engineering 25, 6 (November/December 1999): 800-815.
[17] Krishnan, M.S. Kekre, C. H. Kriebel, T. Mukhopadhyay. 2000. Management Science. 46(6) 745–759.
[18] McGibbon, T. (1999). A business case for software process improvement revised. Data Analysis Center for Software (DACS).
[19] Mehner, T., Messer, T., Paul, P., Paulisch, F, Schless, P. & Volker, A. (1998). Siemens process assessment and improvement approaches: experiences and benefits. 22nd International Conference on Software Engineering (ICSE), 186-195.
[20] Norusis, M. 2004. SPSS 13.0 Statistical Procedures Companion. Upper Saddle-River, N.J.: Prentice Hall, Inc..
[21] Pitterman, B. (2000). Telcordia Technologies: the journey to high maturity. IEEE Software 17(4), 89-96.
[22] Sakamoto, K.; Niihara, N., “Analysis of Software Process Improvement Experience using the Project Visibility Index.“ Software Engineering Conference, Dec 1996, pp.139-148.
[23] SEI, CMMI for Development, Version 1.2, August 2006. CMU/SEI-2006-TR-008.
[24] SEI, Process Maturity Profile, CMMI For Development SCAMPISM Class A Appriaisal Results 2008 End-Year Update, March 2009.
[25] Siegel, S.; Castellan, N. J. Jr.(1989) Nonparametrics statistics for the behavioral science. New York:McGraw-Hill.
[26] SPSS White paper-Technical Report (2001), The SPSS TwoStep Cluster Component.
[27] Subramanian, G.H.; Jiang, J.J.; Klein, G. “Software quality and IS project performance improvements from software development process matureity and IS implementation strategies.“ The Journal of Systems and Software 80 (2007) 616-627.